Oracle VM VirtualBox 歷史版本列表
更新時間：2022-11-19
更新細節：
What's new in this version:
Fixed and/or added:
- VMM: Added nested paging support for nested virtualization (Intel hosts only)
- VMM: Fixed rare guru meditations with certain guests on macOS 10.15 (Catalina)
- VMM: Fixed possible VM process crash on Windows hosts when Hyper-V is used with certain guests
- VMM: Fixed Windows XP guest hang or BSOD on AMD CPUs under certain circumstances
- GUI: Various bugfixes for the Guest Control file manager
- GUI: Added more informative file operations in the Guest Control file manager
- GUI: Added an option to the global settings (the display page) to resize user interface font
- GUI: Fixed a regression in new vm wizard. Selected virtual disks are no longer deleted when the wizard is cancelled
- GUI: Added a new menu item to the devices menu to optionally upgrade the guest additions.
- VirtioSCSI: Fixed recognition of the virtio SCSI controller by the EFI firmware
- VirtioSCSI: Fixed hang when shutting down the VM if the virtio SCSI controller is used
- virtio-net: Workaround a bug in the virtio-net driver included in FreeBSD version up to 12.3 which renders the device non functional
- Storage: Fixed I/O errors with the VirtioSCSI controller when the host I/O cache is enabled
- VBoxManage: Fixed regression when 'createmedium disk --variant RawDisk' command resulted in invalid .vmdk file
- Main: Restored input pointing device behavior in multi-monitor VM configuration
- Main: Fixed progress indication during automatic Linux Guest Additions installation
- Guest Control: Fixed path handling issues
- 3D: Fixed VM process crash on macOS with 3D enabled
- Linux Host and Guest: General improvements in startup scripts
- Linux Guest Additions: Introduced initial support for RHEL 8.7 and 9.2 kernels
- Linux Guest Additions: Introduced initial support for SLES 15.4 kernels
- Linux Guest Additions: Fixed kernel modules rebuild behavior on system shutdown
更新時間：2022-11-10
更新細節：
What's new in this version:
- Fixed incorrect merging of citations in word processor plugins (since 6.0.16)
更新時間：2022-11-01
更新細節：
What's new in this version:
Functionality changed or added:
Automatic merging of adjacent in-text citations:
- Works in Word, LibreOffice, and Google Docs
- To merge citations, make sure they're immediately adjacent, with no spaces between them, and then press Refresh to merge them into a single citation
- Multi-item citations can still be created or modified using Add/Edit Citation
Added “Include Zotero Links” option for Rich Text/HTML Quick Copy and note export:
- Allows pasting of annotations and notes with zotero:// links into editors such as Obsidian that accept rich text by default without needing to force use of plain-text Markdown output (details)
- Automatically locate missing attachments within Linked Attachment Base Directory
- If a linked file can't be found and a Linked Attachment Base Directory is set, check whether part of the current path can be applied to the Linked Attachment Base Directory to locate the file, and offer to relink the file and any other files with the same base path
PDF reader changes:
- Allow importing annotations from files in group libraries
- Keep only 2 tabs loaded on systems with 8 GB or less of memory
- Removed view-only rotation in favor of actual page rotation
- Truncate long text in bubbles in Quick Format citation dialog
- Added additional note font size options in View menu
- Additional sizes still configurable via extensions.zotero.note.fontSize in Config Editor
Fixed:
- Don't match all attachments with annotations for “not” search conditions (since 6.0.15)
- Fixed wrong given name disambiguation after editing author in a given session
- Fixed potential hang or infinite retry from certain website responses when using Find Available PDFs
- Fixed assignment of colored tags using number keys (without Shift) on French keyboards
PDF reader:
- Fixed 'r' key not working inside input fields
- Make full URL clickable when URL contains DOI
- Fixed an issue that could cause some annotation author names to incorrectly appear in gray
- Don't include adjacent colon when double-clicking on words
Note editor:
- Disable rich text inside inline math nodes
- Use same TeX font size inside block and inline math nodes
- Fix full-text indexing of text files with non-.txt extensions (e.g., .md files)
- [Accessibility] Fixed item list row text not being read when using non-contiguous keyboard selection
- Miscellaneous other bug fixes
更新時間：2022-10-21
更新細節：
What's new in this version:
- Improves overall platform stability
- General Timeline and Timecode feature improvements
- General Playback Marker feature improvements
- Improves stability of ASIO audio devices
Fixed:
- an issue where SDI and NDI outputs would stop updating after an indeterminate period of time
- an issue where Media and Audio Playlist Actions as well as Timelines were not respecting if "Always Retrigger" was enabled
- a few issues where some Bible translations would not always return the most accurate information
- an issue where Current/Next Linked Text Objects were not always displaying on Stage Layouts
- an issue where hidden Playlist items were still appearing as the Next Playlist item on a Stage Display
- an issue where Media thumbnails were not updating after removing Effects
- an issue where Media in the Media Bin transitioned to Next one second early
- an issue where standalone Media in a Playlist would not trigger if Network Link was enabled
- an issue where Slide Build Delays would not allow other slides to be Triggered
- an issue where the CPU usage on Windows machines increased while the Preferences window was opened
- an issue where exporting multiple Presentations as Text was combining them all into one file
- multiple issues with Slide Objects that have Scaling, Flipping, or Rotation adjustments applied not appearing correctly
- an issue where hard line returns were being deleted when copying and pasting from a Word Processor
- an issue with API thumbnail requests not being able to return PNG images
- a discrepancy in API response for a Presentation Slide that contains multiple text boxes
- an issue where Macros with a transparent color were not appearing in ProPresenter Control
更新時間：2022-10-21
更新細節：
What's new in this version:
- Support for the ATEM 4 M/E Constellation HD
- General performance and stability updates
更新時間：2022-10-21
更新細節：
What's new in this version:
New features:
- Added support for IAM token based authentication for AWS RDS or Azure DB
- Added support to specify the background fill color to the table nodes in the ERD tool
- Allow reordering table columns using drag and drop in ERD Tool
- Add option to generate SQL with DROP table DDL in ERD Tool
- Added high availability options to AWS deployment
- Expose the Gunicorn limit_request_line parameter in the container, with the default set to the maximum 8190
Housekeeping:
- Use SocketIO instead of REST for fetching database tables data in ERD
- Ensure that the tooltips are consistent throughout the entire application
- Remove Python’s ‘Six’ package completely
Fixed:
- Ensure consistent orderings for ACLS when comparing schemas in the schema diff
- Ensure that the result grid column should take width as pre preferences setting on first execution
- Fixed an exception occur while taking backup and SSL certificates/keys are not found in the specified path
- Fixed intermittent error shown while OAuth2 login
- Ensure that the path to the psqlrc file is correct when multiple users open the PSQL tool at the same time
- Ensure that the continue/start button should be disabled if the user stops the Debugger for the procedures
- Ensure that the query tool creates a new tab with the appropriate user when pressing Alt+Shift+Q
- Added the close button for all the notifications of the notistack
- Added the ability to display the selected text from the query tool in the find/replace box
- Ensure that the search filter should be cleared when a new row is added to the user management
- Ensure that the user management dialog should not allow the same email addresses with different letter casings when creating users
- Fixed XSS vulnerability issues
- Ensure that the scroll position should be preserved for the result set in the query tool on tab change
- Ensure that the default value for a column should be used if it is made empty
- Fixed an issue where user was unable to select privileges in Safari
- Fixed console warning shown while updating database node from browser tree
- Fixed an issue where the prompt is not visible when clicking on the ‘save results to file’ button on the large data
- Fixed error occurring while LDAP authentication for a user with multiple email attributes
- Fixed an issue where notifications disappeared quickly
- Ensure that the correct value should be returned if an exception occurs while decoding the password
- Fixed the issue while downloading the file from the file manager
- Ensure that the login form is hidden if the authentication source is OAuth2 or Kerberos
- Fixed an issue where the password recovery link was not working.Ensure that scroll bar on browser tree should be visible on windows resize
- Fixed the cross-site scripting vulnerability
- Fixed an issue where filtered rows were not working
更新時間：2022-10-21
更新細節：
更新時間：2022-10-21
更新細節：
What's new in this version:
- Main: Fixed issue when VBoxSVC could become unresponsive if Extension Pack was not installed
- Windows host: Shared Clipboard: Fixed issue when only 4Kb of host clipboard buffer was accessible to guest
- Windows hosts: GUI: Fixed missing Qt libraries for vista style and sql driver
- GUI: Fixed a glitch in the log viewer which was causing wrong log file to be saved
更新時間：2022-10-11
更新細節：
What's new in this version:
New Spectral devices, for all Bitwig Studio customers:
- Spectral Suite, four new audio FX and a package of sound content, is now part of Bitwig Studio
- There is a new Spectral device category, where the four new audio FX can be found
- How do these "spectral" devices work?…
- These audio FX are frequency-domain devices, which separate the incoming sound into hundreds of pieces for analysis
- In the frequency domain, each moment of a sound isn't simply loud or quiet (for example); there are always frequencies that are loud and those that are quiet
- So Bitwig does the math and then, based on the device's orientation, related signals are grouped into "channels" for easy mixing and plug-in-friendly control
- These devices are "containers" at heart, reconstructing the original sound… until you move one of the channel controls (Gain or Panning) or insert a plug-in
- The sooner you adjust an audio parameter, the more obvious the devices become
- All four devices have an identical structure for each channel:
- Gain control, in standard volume range
- Panning control, for stereo placement
- An On (or "active") switch, shown with a speaker icon beneath the Gain knob, in case you want to disable a channel
- A Solo control, shown as an S button to the left of the Gain knob, for auditioning one channel at a time
- A device chain, for processing this channel of audio with any Bitwig device or VST/CLAP plug-in
- Like all nested device chains on these devices, notes reaching the device are available here, for envelope triggers, phase resets, or anything else you deem appropriate
- All four devices also share an identical Output Section:
- A Pre FX chain, for processing incoming audio before it goes to the spectral analysis, perhaps for a Compressor or Dynamics to tighten the signal, or anything else
- A Post FX chain, for processing the sum of the audio channels, maybe for an EQ+ to balance the full output, or your favorite plug-in, or…
- A Mix control, that blends the dry incoming signal with the final processed signal (coming from the channels and Post FX chain)
- Freq Split, Loud Split, and Harmonic Split all use similar visualizations and share a Spectrum Display Inspector parameter, with two modes:
- Pre shows the analysis data (and no audio processing from the channel controls, such as Gain or audio plug-ins), good for tweaking the splits
- Post shows each channel's output audio, post-processing
New Spectral Suite device: Freq Split (Spectral):
- Divides signal into frequency groups and sorts them into one of four channels, for individual mixing and processing
- Frequency Splits sets the number of splits across the frequency spectrum, which works with two nearby parameters:
- Split Insertion Direction sets whether additional splits are added from the right/high edge of the spectrum (←), from the left/low edge of the spectrum (→), or around the relative middle (↔︎)
- Crossfade Amount determines the overlap between splits
- So with the device's default settings, 16 Splits with an Insertion Direction putting new splits on the right (←) means:
- The 1st, 5th, 9th, and 13th splits land in channel 1 (red)
- The 2nd, 6th, 10th, and 14th splits land in channel 2 (blue)
- The 3rd, 7th, 11th, and 15th splits land in channel 3 (yellow)
- The 4th, 8th, 12th, and 16th splits land in channel 4 (magenta)
- And if the Crossfade Amount was increased from 0.00 % (full isolation between bands) to 50.0 %, then each split would spend its first 25 % crossfading with the previous split, and its last quarter crossfading with the next split
- Split Nudge slides the frequency splits by an offset value, so a setting of +2.00 pushes the contents of channel 1 into channel 2, channel 4 into channel 2, and so on
- Split Spin also slides the frequency splits but relative to the entire spectrum; so a setting of -10.0 % slides all the splits a tenth lower in the entire spectrum
- Whether being subtle (Split Nudge) or extreme (Split Spin), modulating either of these parameters shows the "filter bank" quality of this device, creating new phasers and more when each channel is loaded with different audio FX
- Split Bend curves the frequency split pattern around a new midpoint, either moving the midpoint downward and putting splits closer together in the lower frequencies (negative values) or moving the midpoint higher and having splits closer together in the upper frequencies (positive values)
- Split Pinch kinks the frequency split pattern, either bunching more splits around the midpoint (positive values) or putting more splits into the sides (negative values)
- In the device's display, the interactive white dot controls Split Bend when dragged left to right, and Split Pinch when dragged up and down; it's fun
- The Spectral Limiter option sets a maximum Threshold level for each individual frequency bin
- In the device's display, the Threshold is shown with a horizontal orange bar that can be dragged up or down
New Spectral Suite device: Harmonic Split (Spectral):
- Tracks the fundamental frequency of the incoming sound, for splitting Nonharmonics (gray) to one channel and dividing harmonics between Harmonics A (orange) and Harmonics B (turquoise) channels, for individual mixing and processing
- Harmonics Pattern decides how harmonics are distributed between the A and B channels
- The default setting of 2 places every 2nd harmonic in A channel, so the A channel will be odd harmonics (1st, 3rd, 5th, etc.), and the B channel receives all even harmonics (2nd, 4th, 6th, etc.)
- A setting of 4, for example, would place the 1st, 5th, 9th, etc. harmonics in channel A, and all other harmonics (2nd, 3rd, 4th; 6th, 7th…) into channel B
- Higher values lead to narrower results in the A channel — and the potential for more extreme processing without "getting into trouble"
- A setting of 1 is special, routing only the fundamental to channel A and all other harmonics to channel B
- Nonharmonic Sensitivity is a relative control for how picky the harmonic vs. non-harmonic split is, where a higher Sensitivity value allows less audio into the Nonharmonic channel — and more audio into the two Harmonics channels
- The Maximum Harmonics Inspector parameter allows you to limit the number of harmonics being tracked, acting as a "ceiling" when you want fewer frequencies in the Harmonics A and B channels
- Fundamental tracking can be adjusted with several analysis parameters:
- Tilt favors the high frequencies (when positive) or low frequencies (when negative), useful when the desired fundamental is filtered in the sound, etc.
- The Low-cut Frequency and High-cut Frequency parameters narrow the frequency tracking area
- An amplitude Detection Threshold can be set, keeping moments that stay below that level in the Nonharmonics channel
- In the device's display, the Detection Threshold and Cut Frequencies are interactive lines that can be dragged
- The device display also illustrates the currently-detected fundamental with a white dot and moving crosshairs
New Spectral Suite device: Loud Split (Spectral):
- Uses two thresholds to separate the Quiet (green), Mid (yellow), and Loud (red) portions of the incoming sound, for individual mixing and processing
- A Higher Threshold (red) sets the level where stronger signals are considered Loud
- A Lower Threshold (green) sets the level where weaker signals are considered Quiet
- In the device's display, both thresholds are visualized as horizontal lines, which can be dragged up and down
- When clicking a line's dot handle on the right, only the outer band of that threshold will be heard while the mouse is held
- Any signal falling between the two thresholds is considered Mid
- Relative Loudness Mode follows the level of the incoming sound, treating 0.0 dB as the strongest band at any given moment
- Relative Loudness Mode uses separate Relative Higher Threshold and Relative Lower Threshold parameters
- Each threshold has its own Knee value, for setting the transition (and effective crossfade) between adjacent channels
- In the device's display, ALT-dragging on either threshold adjusts its Knee parameter
- Rise Time sets the number of blocks before a softer signal fully transitions up into a louder band, like a "resistance" parameter
- Fall Time sets the number of blocks before a louder signal fully falls down into a quieter band, like a "decay" parameter
- Tilt is an analysis parameter, favoring the high frequencies (when positive) or low frequencies (when negative) before the channel splitting is applied
New Spectral Suite device: Transient Split (Spectral):
- Separates the Transients (short, unstable sounds; colored yellow) and Tones (periodic or pitched sounds; colored blue), for individual mixing and processing
- Analysis Bias either skews the detection to favor Transients (positive values) or Tones (negative values)
- The Transient Type Inspector parameter switches between two different algorithms for which type of Transient is being looked for:
- Percussive searches for typical impact transients, good for drums or other things that "click" and "smack"
- Noise looks for noisy smears, or even reverb residue
- Transients Decay sets a time (in blocks) for extending detected Transients, allowing them to release
- Tones Smoothing sets a time (in blocks) for extending detected Tones, allowing them to decay
- Tilt Amount is an analysis parameter that is colored yellow as it is oriented to how it affects the Transients channel; its effect is the opposite for the Tones channel
- The Tilt Mode Inspector parameter changes the method of Tilt applied, between a Standard model that favors the Transient channel's high frequencies (when positive) or its low frequencies (when negative), or a Contour approach that subtly adjusts the mid frequencies vs. the highs & lows
- Transient/Tones Blend is the audio balance at the output of the spectral section, before each signal reaches its channel
- The Display Style of this device is unique, with two modes:
- Waveform shows a split amplitude domain representation of the two groups
- Sonogram offers the recent frequency-domain history for each group
New Features:
- There is now a Japanese translation of the Bitwig Studio v4.3.0 manual
- Device context menus have be reorganized so that device-specific entries come near the top of the list (for example, the Spectrum Displays setting for three of the Spectral devices)
更新時間：2022-10-11
更新細節：
What's new in this version:
GitKraken 8.10.0 (64-bit)
Improved:
- GitKraken Client has been updated to Electron 17
- New Tab layout has been rearranged to make it easier to access Repositories, Workspaces, and the Terminal Tab
- You can now double click a section header in the left panel to maximize that section. This option is also available in a context menu.
Fixed:
- an issue where the breadcrumb in Azure repo tabs would direct users to add the repo to a Workspace when this is not supported
- an issue where the SSH key options were not being displayed for Azure and self hosted integrations
- an issue where the Workspace Overview page would say there are no PR’s/issues during initial loading
GitKraken 8.9.1 (64-bit)
- Fixed an crash on some Windows machines when opening the Preferences menu
GitKraken 8.7.0 (64-bit)
New/Improved:
- We hemmed in some new threads
- Watch v8.7 feature demo ????
- GitKraken Client now supports the ability to create and apply patches
- Create patch from commit(s)
- Create patch from uncommitted file(s)
- Create patch from Command Palette
- Apply patch from Command Palette
- Left panel improvements – Left Panel now has a context menu to toggle visibility of the different sections
- New Tab update – Updated UI and layout
- Terminal Tab – Repo aliases will now show in Terminal Tab titles
- More fuzzy search – Enabled fuzzy search in gk history and gk blame commands in GitKraken CLI.
- Search tabs list – Users may now search tabs by repo alias in the tabs list
- Naming branch from issue – When viewing an issue from inside GitKraken Client, there is now a short text field for naming the branch when creating a branch from the issue.
Git LFS performance improvements:
- Users will see faster performance when cloning LFS repositories with submodules
- Users will note much faster performance for general GitKraken Client actions, e.g. reset, merge
Fixed:
- We’ve stitched up a few loose ends
- Fixed issue related to GitKraken CLI’s autocomplete in Git Bash
- In Workspaces, users will be notified if attempting to open a deleted or unreachable repo from the repo details section
- Fixed task lists for GitLab issues showing
- Commit graph will immediately update when the app performs a fetch or force push from the terminal
- Fixed issue where if two profiles both have the same repo tab open, switching profiles would cause issues to disappear from the left panel
- Changing accounts will now properly reset the selected Workspace
- In the Workspace Pull Request section, removing a filter and quickly selecting a PR will no longer generate a blank screen
GitKraken 8.6.0 (64-bit)
New:
- You've got a friend in GitKraken
- Users can now create Workspaces using Bitbucket Server repos
- Users can now select Git Bash as their default shell in Windows for GitKraken CLI
- Users can set Git Bash as their default terminal by navigating to Preferences → Terminal → Default Terminal and selecting "Git Bash" from the dropdown menu
- Repo and Terminal Tab aliases
- Users can now set an alias for a repository
- To set an alias, users can right-click on a Repo Tab and select the Alias repository option
- Setting an alias through a Repo Tab will cause GitKraken Client to store that name for the repo and reference it as an “Alias Repository”
- Users can set an alias for individual Terminal Tabs
- To rename any Terminal Tab, users can right-click on the tab and select the Rename tab option
- Setting an alias to a Terminal Tab results in only renaming that specific tab
- Users can now set GitKraken Client to skip submodule updates while performing Git actions, either globally or per repo
Improved:
- Faster for LFS, big repos, and beyond
Git LFS performance improvements:
- Users will see faster performance when cloning LFS repositories
- Users will note much faster checkout times in LFS repositories
- Sections in the left panel will now be collapsed by default
- Users can now set the maximum number of commits shown in the Commit Graph as low as 500 commits
- To set the shown commit limit, navigate to Preferences → General and look for Max Commits in Graph towards the bottom of that menu
- Users will note improved performance when the open repo has a large number of stashes
- When creating a pull request from a branch that starts with an issue ID (e.g, GK-123-feature-branch), a link to the associated issue will now be added to the pull request description automatically
Fixed:
- You are a sad, strange little bug, and you don't have my pity
- When creating a new branch from an issue, users will see the input box as expected
- When working with remote branches in the left panel, the context menu will remain available
- GitLab avatars will now more consistently display correctly
- Branches will immediately refresh when a checkout is performed in a Terminal Tab
- Users connected to an Azure DevOps integration using Azure's older hostname style (eg. {organization}.visualstudio.com) will now be able to use Workspaces and the Pull Requests section in the left panel
- Users leveraging Azure DevOps Workspaces will no longer see a misleading ‘Add a Repository’ button in their Workspace. Users will need to visit Azure DevOps directly to add repositories to their Workspaces
GitKraken 8.5.0 (64-bit)
New:
- Git is what gives a dev their power...It binds the galaxy together
- GitKraken WorkSpaces now support Azure DevOps repositories
- Any Workspace created for Azure DevOps will automatically include repos for a selected Azure Project
- Workspaces can currently support up to 100 repositories for an Azure Project
- Visual interactive rebase can now be initiated from the GitKraken CLI, which you can access from a Terminal Tab or a Repo Tab by clicking the Terminal icon in the top toolbar
- Users can type either gk rebase -i or gk rebase --interactive along with two refs to open the interactive rebase view. If only one ref is passed it will perform the rebase of the branch currently checked out onto the specified ref.
Improvements:
- An elegant Git client for a more civilized age
Git LFS Improvements:
- Users will experience a reduced delay in updating the graph and commit detail panel when selecting commits in LFS enabled repos
- NoteSignificant work towards reducing checkout times for LFS repos is underway and we plan to include these improvements in the GitKraken Client v8.6.0 release, scheduled for June
- When creating a new Team, members can now be added as part of the creation process
- Team members are now sorted by username in the Teams section, found in the left panel of GitKraken Client
Improvements to GitKraken Workspaces:
- Workspaces can now be shared as Team Workspaces, allowing users to share the Workspace with specific teams within their Organization
- In the Workspaces Repository view, clicking on the name of a repository will open it in a Repo Tab
- Users can view repository information by clicking on the Open Repository Details option, found on the right side of the Repositories view
- Organization admins and owners will see a new "Show All Workspaces" checkbox, allowing a simplified way to see all available Workspaces
- Users can now leverage GitHub’s search syntax when using the Workspaces Pull Requests view search
Users will find more options for filtering in the Workspaces Pull Requests view. The new options include:
- "Opened by Me", to show pull requests that were opened by the user. This filter is available for GitHub, GitHub Enterprise, GitLab, and GitLab Self-Managed repositories.
- "At Risk", to show any pull requests that are not drafts and have been open for longer than 7 days. This filter is currently only available for GitHub, GitHub Enterprise, GitLab, and GitLab Self-Managed repositories.
- "By repository", to limit the view to a single repo within the Workspace. This filter is currently available for Azure DevOps, GitHub, GitHub Enterprise, Gitlab, and Gitlab Self-Managed repositories.
- For Windows users, GitKraken Client will now respect the core.longpaths setting in .gitconfig. Previously, GitKraken Client had its own longpaths setting independent of the user’s .gitconfig setting.
- On Windows, core.longpaths now only applies to the files in the working directory, not in the .git directory, to maintain compatibility with Git for Windows
GitKraken CLI autocomplete will now be able to suggest more than one argument in these commands:
- git add
- npm install
- npm remove
- yarn add
- yarn remove
- Notifications with a Call to Action will now be marked as read when the CTA is clicked
Users encountering merge conflicts can now right-click on the conflicts shown in the Commit Panel to reveal new options for easier and faster conflict resolution. The new options available are:
- "Take current", which applies the changes from the branch currently checked out to resolve the conflict
- "Take incoming", which applies the changes from the incoming branch to resolve the conflict
Fixed:
- Bugs…You will never find a more wretched hive of scum and villainy
- GitKraken Client will now open as expected for users on OpenSSL 3 Linux distributions such as Ubuntu 22.04 and Fedora 36
- Users will see increased performance when opening a commit diff for very large images. Large images will now display as a binary file Instead of producing an error
- For large files, such as images and other media, we recommend using Git LFS
- Dotted graph lines will no longer take precedence when overlapping with solid lines in graph views
- Users can now type in the GitKraken Terminal as expected on a wider range of OS versions
- When un-hiding a remote, users can continue hiding or un-hiding remotes without waiting for the triggered automatic fetch to resolve
- Azure DevOps integrations and all self hosted integrations will now work properly on our new Teams license tier
- Users with hundreds or thousands of Azure DevOps Projects will see improved performance when integrating Azure DevOps
- Users can now use quotation marks when naming Workspaces
- All Organization and Team actions will remain available after using the login screen
- The scrollbar in the GitKraken Terminal will now remain clickable in all situations
- When a user pushes many files up at once to GitHub, they will no longer experience an OAuth infinite loop
- Opening repositories via gitkraken --path when GitKraken is already open will now work as expected
GitKraken 8.4.0 (64-bit)
- I pity the tool that does not have Workspaces or the GitKraken CLI
GitKraken Workspaces:
- Workspaces now include a Pull Requests view
- Users can filter PRs to see items "Assigned to me"
- At-risk pull requests are highlighted through a label and filterable
- Selecting any GitHub pull request now shows the user a new Pull Request view that presents users options to quickly manage PRs across a whole Workspace
- Clicking on any repo in a Workspace now shows see more info and options. Users will see the repository's README, as well as quick access buttons to open the repository in a Repo Tab, Terminal Tab, or on the remote repository's hosting provider.
GitKraken CLI:
- The Terminal button in a Repo Tab’s toolbar will now open the GitKraken CLI inside a Terminal Panel, instead of opening a new Terminal Tab. Users can still open new Terminal Tabs through a New Tab, the Command Palette, or through any Terminal’s context menu.
- Users can toggle the Terminal Panel on and off by pressing the Terminal button in Repo Tab toolbar, through keyboard shortcut Ctrl+`, the Command Palette, the Terminal Panel’s context menu, or options in the GitKraken Client's View menu. Toggling the Terminal Panel will turn it on or off across all Repo Tabs.
- A Terminal Panel session can also be terminated by executing the exit command. This will only close the Terminal Panel and not the Repo Tab. Toggling the Terminal Panel back on will initialize a new terminal session.
- Unlike with the Terminal Tabs, navigating to a different working directory in a Terminal Panel will not change the repository opened in the Repo Tab
The following gk commands are available in the Terminal Panel:
- gk blame
- gk diff
- gk history
- gk help
Improved:
- Making GitKraken Client a mean, clean Git managing machine
- Users will now see helpful icons when shown GitKraken CLI Autocomplete suggestions, helping clarify to which command the suggestion is related.
- Git LFS users will see improved performance checkouts.
Fixed:
- Filtering Autocomplete suggestions by name will work as expected
- After selecting between multiple Autocomplete suggestions that have the same prefix, further suggestions will disappear as expected
- Users will no longer be allowed to create Workspaces for repositories on unsupported versions of GitLab Self-Managed services
- Bitbucket Server users will now see the branches correctly populated when creating Pull Requests
GitKraken 8.3.3 (64-bit)
Improved:
- Users creating an account or signing in will see an improved user experience
GitKraken 8.3.2 (64-bit)
Fixed:
- GitKraken Client now supports GitHub’s new GraphQL query types. GitHub users will now see creating, commenting and reviewing pull requests work as expected.
GitKraken 8.3.1 (64-bit)
Improved:
- Though short, February is filled with lots of love and sweet improvements
GitKraken CLI:
- Users who want to use the GitKraken Terminal when opening repositories in external terminals, alt/⌥ + T, can now set this as the default by navigating to Preferences → General → Default External Terminal and selecting "GitKraken Terminal" from the dropdown menu.
- When hiding the visualization panel orientated to the top of the window, the toolbar will remain in place at the top
Themes:
- Users can customize the terminal colors together with the rest of their custom themes. This update removes the Terminal Theme setting from the Preferences → Terminal menu.
Fixed:
- The early birds of spring get the bugs
- GitKraken Client will remain responsive when adding an issue tracker integration supporting a large number of assignable users
GitKraken 8.3.0 (64-bit)
New:
- I got a need…a need for speed
- GitKraken Client v8.3 introduces a new ARM64 compatible version, offering native support for Apple Silicon architectures, as used in Macs with M1 chips.
- GitKraken Workspaces are now available for repositories hosted on GitHub Enterprise and GitLab Self-Managed.
Improvements:
- There are no speed limits on the road to success
- Mac users will get optimal performance without needing to run the 'Big Sur workaround' from a terminal, which had been required to fix the partial signature issue introduced in macOS Big Sur.
- Fedora 35 users will no longer need to pass the --no-sandbox flag to launch GitKraken Client
gitKraken CLI:
- New Terminal settings added under Preferences → Terminal
- Default Directory - Users can now set the default directory where new Terminal Tabs will open when initiated from the "New CLI Tab" button in the Repo Management Tab or from the Comand Palette.
- Line Height - Users can set how much space appears between each line printed to the terminal
- Autocomplete suggestions have been added for git flowcommands
- Any user created global or local Git aliases will be shown as autocomplete suggestions
- The git reset command will now suggest staged files too
- Autocomplete suggestions for git add will show relative paths when called from inside a subfolder
- The visualization panel will automatically open after making the initial commit in a new repo
- Right mouse clicking in a Terminal Tab will open a new context menu allowing users to open new Terminal Tabs, paste into the terminal, and close the terminal, among other actions
Themes:
- Users can customize the commit graph colors in their custom themes. Examples of // graph colors have been added to the default theme files. Users can refer to Preferences → UI Customization -> Theme to locate the GitKraken Client theme folder on their computer.
Fixed:
- You take a crash, you get back up, and next time you succeed. That’s a great feeling.
- Pull requests filtering in the left panel is no longer case sensitive
- Users on GitLab Self-managed +13.8 will no longer get directed to a 404 page when selecting Generate a token on GitLab
- When using the Pull Request panel for forks using Azure DevOps based repositories, users will no longer see a no options error on the form
GitKraken CLI:
- Using reverse search (ctl+r) will no longer cause unintended autocomplete suggestions
- Updated autocomplete suggestions for git gc, fixing spelling issues
- Autocomplete suggestions for paths with spaces in them have been improved
GitKraken 8.2.1 (64-bit)
Improved:
- The Workspaces tab can now be closed to save space in the tabs bar while not in use. A small icon has been added to quickly reopen the tab when needed.
GitKraken 8.2.0 (64-bit)
New:
- We have helped users progress and seen them accomplish wonders
- Introducing GitKraken Workspaces
- GitKraken Workspaces save teams time by providing an easy way to group repositories, take actions against multiple repositories at once, and quickly onboard new team members
- GitKraken Workspaces allow you to gather and access all the required repos for your project in a single tab in the GitKraken Client. The new GitKraken Workspaces tab shows you the status for the last branch that you checked out, how far ahead and/or behind in commits you are, and if there is an active WIP for each included repository.
- GitKraken Workspaces can be created as Personal, only visible to you, or Shared, visible to all members of your Organization
- Users can access GitKraken Workspaces from the new “Workspaces” tab in the tabs bar, from the New Tab view, from the command palette, which can be opened with the keyboard shortcut cmd/ctrl + p, or from the newly added repository breadcrumb in any Repo Tab.
Users can view details and trigger the following actions on any or all of the repositories in a workspace at once:
- Clone multiple repositories at once. This will help teams quickly onboard a new team member or get a new computer up and running
- View the last checked out branch for all repositories and see if a branch is ahead/behind a remote
- View work in progress for all repositories, including the number of files modified, added, renamed, or deleted
- Perform a fetch for all or a selection of repositories
- Open multiple repos in the GitKraken Client, or in an external editor, such as VS Code, IntelliJ, Atom, or Sublime Text
- Open any repository in the associated hosting service website
- GitKraken Workspaces can currently contain repositories hosted on GitHub.com, GitLab.com, or Bitbucket.org
Themes:
- Users may now create their own custom GitKraken Client themes
- For more information about creating a new custom theme, checkout our Themes documentation or navigate to gitkraken/themes/README.md
- Users will find two new themes when navigating to Preferences → UI Customization menu
- Users can now sync their GitKraken theme with their system theme, if their OS supports it
Activity status:
- An activity status will now display on the avatars of members in your GitKraken Organization or Team, indicating if they are actively using the GitKraken Client. This activity status icon is visible in the Team View section in the Left Panel, or in the Organization view in Preferences.
- Users can manually set their status to “Active” or “Away” by selecting the circle icon in the top right corner, or by opening the Profile/Account dropdown menu
- GitKraken Workspaces and Activity status are currently unavailable for Self-Hosted and Stand-Alone customers
Improvements:
GitKraken CLI:
- Users can now customize the behavior of the ↹ Tab key when using auto-complete in a Terminal Tab. This setting can be found under Preferences → Terminal → Tab Behavior.
- Users can customize the cursor used in a Terminal Tab. This can be configured in Preferences → Terminal → Cursor Style. Users can select either Block, Underline or Bar for their cursor.
- Auto-complete suggestions will now show branches and tags as options when running git diff or git reset commands
- The gk diff command now supports tags and branches as options
- Auto-complete suggestions have been added for npm and yarn
- When users open the pull request panel and click on a pull request while the left panel is minimized, the GitKraken Client will now open the pull request view
Fixed:
- We came here years ago to protect users from these bugs
- When using the GitKraken CLI, suggestions will disappear as expected after auto-completing a command with escaped characters in the path
- After using the GitKraken Client to execute a cherry-pick and resolving any arising conflicts, the Git CLI will no longer report that a cherry-pick is currently active
- When creating a pull request in a repository with a large number of forks, users will no longer have to wait as all forks are being fetched before opening the dropdown menu
GitKraken 8.1.1 (64-bit)
Improved:
- Sudon't want to miss out on these new improvements
GitKraken CLI Preview:
- GitKraken CLI users can now use git help to display help information about using Git
- Windows users will now see an auto-suggest option for the cd command
- Users changing directories in the GitKraken Terminal will see auto-suggest options showing the end of the folder path rather than just the beginning. This is useful when long directory names are present.
- Users can choose from more Keif options for their avatars when creating or editing their Profiles
Fixed:
- There are only 10 kinds of bugs: the ones we have fixed and the ones that we have not identified yet
GitKraken CLI Preview:
- Improved GitKraken Terminal support for custom fonts, such as Nerd Fonts and Powerline fonts
- Users leveraging oh-my-posh in Powershell using custom themes will now see and be able to select auto-suggest options
- Users can now resize the commit panel in a GitKraken Terminal tab
- All Mac users are now able to use the gk commands
- Windows users leveraging “Constrained” language mode in Powershell can now execute gk commands
- Users can now resize the merge editor tool as expected when the visualization panel is positioned to the left or right in a GitKraken Terminal tab
- When working with GitHub and GitLab wiki repos, GitKraken will no longer throw an error message about being unable to fetch pull requests
- If a user checks out a commit while in Solo mode, they will now see the HEAD tag displayed
- Users fetching GitHub pull requests will no longer see timeouts
Stand-Alone & Self-Hosted:
- There is no place like ~
- The GitKraken CLI Preview is now available for Self-Hosted and Stand-Alone customers
GitKraken 8.1.0 (64-bit)
New:
- The seasons continue to change and so does GitKraken...for the better
- The GitKraken Git client can now identify weak SSH keys and provide an easy way to remove and replace them
Improvements:
- It's the time of year to reap the harvest of new improvements to the GitKraken Git client
GitKraken CLI:
- GitKraken CLI users can now use reverse search as expected by typing Ctrl+R in the terminal
- Mac users will now see the LANG environment variable pass automatically to the shell process
- When selecting an auto-suggest option with the mouse, GitKraken will now refocus on the terminal prompt
- The GitKraken CLI now supports 256 colors
- Mac and Linux users will now see auto-complete suggestions for the cd command
- When running gk blame or gk history, users will now see suggestions when navigating from inside a repository's subdirectory after typing ../
- Users will now see auto-suggest options for the git gc command
- In addition to showing or hiding the visualization panel, users can now orient it to the top, bottom, left, or right, as well as toggle the right-side commit panel using the visualization panel toolbar
- The user interface for user profile settings under the [Preferences] menu has been improved
- Users can now open specific comments on GitHub.com from the comments inside GitKraken's pull request or issue views
- Users who are not using GitKraken Integrations will no longer be repeatedly prompted for credentials for each remote when connected to repositories with multiple remotes sharing the same hostname
Fixed:
- As the leaves fall, so do these bugs
- The overall reliability of notification delivery has been improved
- Auto-complete for Windows users leveraging the GitKraken CLI has been improved
- Windows users will no longer see a Named Pipes error when running gk commands in a terminal tab
- Using gk diff in the GitKraken CLI will produce properly parsed numerical SHAs
- When discarding a large number of files in a repository, the repo will fully load as expected
GitKraken 8.0.1 (64-bit)
Improvements:
- GitKraken users can now search for a particular tab and navigate the menu using the keyboard when using the tab dropdown menu
Fixed:
- Gitflow branch folders and tag folders collapse and expand as expected when selected in the left panel in GitKraken
- Layout and options have been optimized in the Organization panel in GitKraken's Preference view
GitKraken 8.0.0 (64-bit)
New:
- Introducing the GitKraken CLI Preview
Deep Linking:
- We've added the ability to share deep links to specific remote repositories, commits, branches, and tags in GitKraken. This allows users to more easily collaborate and save time when working in issue queues or Git pull requests.
Jira App Integration - Git Integration for Jira:
- GitKraken now works with the Git Integration for Jira app to allow quick navigation between GitKraken and Jira when viewing commits and file diffs related to Jira issues
Improvements:
- The Fuzzy Finder is now the Command Palette!
- Tab navigation has been significantly improved when many tabs are open at once
- Reopening tabs after a “close all tabs to the right”, a “reopen closed tab” will now reopen only one tab at a time, instead of all that were closed at once
- An option to “Quote Reply” has been added for comments in the PR view
- The profile menu now shows the Organization associated with the current profile
- A “Cancel Rebase” button has been added at the top right of the Interactive Rebase panel for easier access
- We have improved form, prompt, and modal keyboard navigation and submission
- Improved user experience for the login form
Fixed:
- Styling of long branch names in the right panel has been improved
- Users will no longer see issues for remotes without access to a repo, as happens when users leave an organization or when forks are deleted
- When using the delete key to erase spaces in a URL, the cursor will behave as expected
- The Pull Request icon has been added back to branch labels in the graph
- The bottom of Diff views are no longer cut off when the file mode changes
- Relative paths are now allowed in hooksPath
- All users are now able to select a project for GitLab and GitLab-Self-Managed issues on the left panel
- If Sublime Text 4 is installed, it will now be detected and appear in the external editor dropdown
- Debouncing has been added in the left panel search. Searches will be executed when you stop typing, instead of on each letter, making it easier to find what you’re looking for.
GitKraken 7.7.2 (64-bit)
New:
- Users who are leveraging Git hooks in their workflows will be happy to learn that GitKraken now supports the Git configuration core.hooksPath variable. Users can also change the directory for where a repository’s hooks are stored from inside GitKraken by navigating to Preferences → Git Hooks.
Improvements:
- We’ve improved performance for the new GitKraken Teams features. Users will notice that repository actions respond faster, especially for larger repositories.
Untracked files will no longer appear in the GitKraken Teams Panel if those files have not been modified.
Fixed:
- GitKraken Merge Conflict Editor users can now scroll horizontally, even if the scrollbar is over a conflicted line
- When switching tabs, GitKraken will now remember what panes users had collapsed, as well as which branches & tags had been hidden
GitKraken 7.7.1 (64-bit)
Improved:
- All users will notice improved performance when switching between tabs in GitKraken
- The Author and Team filter lists are now sorted alphabetically by default, making it easier to find what you are looking for
Fixed:
- When opening repositories in GitKraken, users will no longer get stuck on the loading screen
- GitKraken users will no longer encounter a loop repeatedly asking for their SSH passphrase
GitKraken 7.7.0 (64-bit)
New:
- Talent wins games, but teamwork and intelligence win championships…
- Introducing GitKraken Teams
- GitKraken users with Pro and Enterprise Cloud accounts can now create and manage teams within their organization
Organizations are now visible in Preferences in each user's Profile. From this view:
- All team members can view a list of other members in the organization, as well as the members in any team to which they belong
- Administrators can create and manage teams
- Administrators can also invite, remove, or change the role of members in an organization.
- Team collaboration features
- Team View
- View a list of members in your team in the left panel
- See which files and branches your fellow team members are currently working on
- To avoid merge conflicts, files you and a team member both have changes on are marked with a warning icon ⚠️.
- Graph filtering. Filter the Author column of the commit graph by Team and/or collaborators to highlight work committed by your team.
New Pull Request section:
- Pull request filtering
The following filters are included by default to help focus PRs most important to users, with some options specific to certain hosting providers:
- My Pull Requests
- All Pull Requests
- Assigned to me
- Awaiting my review
- Custom filters can also be created for all supported integrations
- All filtered pull requests can now be easily searched
- New status icons will now indicate CI/CD status as well as request status of pull requests, depending on the hosting provider
Improvements:
- It is literally true that you can succeed best and quickest by helping others to succeed…
- Diff hunks are now copyable from the Pull Request view
- Updated and new GitHub Actions templates
- Any form submission will now be focused, making for more convenient submission with tab/enter
Fixed:
- We think, mistakenly, that success is the result of the amount of time we put in at work, instead of the quality of time we put in…
- Commits from interactive rebases will resume being signed
- Tab navigation issues resolved
- Notifications settings will no longer always be detected as offline
- The merge tool window will no longer extend off the right of the screen
- When in a detached head state the pull dropdown is now enabled to allow fetching
Notes:
- If I have seen further, it is by standing on the shoulders of giants...
- GitHub is deprecating user/pass authentication, we have added an in app notification to prepare users of this upcoming change
GitKraken 7.6.1 (64-bit)
Fixed:
- Resolved an issue that was preventing some repositories from rendering when connected to GitLab Self-Managed
GitKraken 7.6.0 (64-bit)
New:
- Github.com users may now utilize the Pull Request view! Selecting a pull request in the left panel will bring up the pull request view which will allow users to:
- Edit the pull request title, description, reviewers, assignees, milestones, and labels
- Comment on a pull request
- Merge a pull request from GitKraken
- Submit reviews by leaving a comment, approving the PR, or requesting changes
- GitKraken users at all plan levels can now create and edit issues on GitHub and GitLab public repositories
Improvements:
- The cherry pick option has been removed from the context menu that appears after selecting multiple commits in the graph. GitKraken does not support the ability to cherry pick multiple commits...yet
- Markdown and styling have been improved throughout the application, most notably in issue detail view and the in-app release notes
- The scrollbar in the hunk diff view has been improved so it is selectable in all cases
Fixed:
- Scrolling through a list of tracked LFS file types will feel smoother and render correctly
- The left panel will no longer disappear if a GitHub workflow file contains only content that has been commented out
- Pull request information will no longer render multiple times, and text artifacts will no longer clutter the left panel
- The diff and issue detail views can no longer be opened simultaneously when the commit panel is pinned to the bottom of the screen
- The .gitignore file generated when initializing a repository form GitKraken will no longer be set as read-only
GitKraken 7.5.5 (64-bit)
Fixed:
- Resolved an issue that was causing GitKraken to sporadically crash on Mac and Linux when performing certain actions
- Fixed another crash that could occur when performing checkout operations
Notes:
- In an upcoming release of GitKraken, the minimum supported version of GitHub Enterprise will be 2.20.24 in order to use the integration. We anticipate this change to go live at the beginning of May.
GitKraken 7.5.4 (64-bit)
- Resolved an issue that was causing GitKraken to crash for some users when trying to push
GitKraken 7.5.3 (64-bit)
Fixed:
- Using HTTPS over a proxy will no longer incorrectly throw the error message: Failed to get server certificate: The handle is in the wrong state for the requested operation
- Hitting the Delete button in the commit message box when a commit template is present will no longer generate new lines
- The cursor will no longer jump to the end of the line when typing in a feedback or support form
- Repositories containing empty annotated tags will no longer cause GitKraken to crash on Mac and Linux
- Squashing in interactive rebase will no longer cause GitKraken to deadlock
- The error message: Failed to initialize [object Object] will no longer appear for GitLab users
- Error logs can again be opened using the File menu
GitKraken 7.5.2 (64-bit)
Improved:
- The tooltip display has improved when dragging-and-dropping branches in the left panel
- If a WIP node is present when a user selects Reset Local to Here to checkout a remote branch, GitKraken will now create a stash
- The profile dropdown menu will now close after switching profiles
Fixed:
- Relative timestamps will display correctly in the graph
- Desktop notifications will render as intended
- A newline can now be prepended to the commit description field
- The option to delete a remote tag will again appear when deleting subsequent tags after deleting a tag from a remote repository
GitKraken 7.5.1 (64-bit)
- critical stability improvements for syncing GitKraken notifications
GitKraken 7.5.0 (64-bit)
New:
- A notifications system has been added to GitKraken to alert users of important messages such as version updates, bug fixes, and more helpful information. These notifications can be accessed via the bell icon ???? in the upper right corner, and notification settings can be configured via Preferences Notifications
Improvements:
- The hamburger menu in the upper right corner has been removed. Preferences can now be more easily accessed through a new gear icon ⚙️
- The profile dropdown menu has been redesigned to better distinguish a user's Git authoring details from their GitKraken account details
- Users will now see the options to Show/Hide when multi-selecting local branches and stashes from the left panel
Bug-Fixes:
- Actions accomplished by tab-related keyboard shortcuts will no longer be duplicated
- Users can again toggle the left and commit panels from the View menu options
- The left panel will no longer disappear if users have an empty yaml file in their repository’s github/workflows/ folder
GitKraken 7.4.1 (64-bit)
Improvements:
- After a commit action has been made in GitKraken, a timestamp showing the duration of the action will be added to the activity log
Fixed:
- The GitLab Self-Managed issue tracking integration will work for instances that have a URL path or protocol
- Fetching and auto-fetching while a file is open in GitKraken will no longer reset the scroll position on the Monaco text editor
- Stashing while the WIP node is selected will select the parent commit
- Post-checkout hooks will run correctly when starting a Gitflow Feature, Release, or Hotfix branch
GitKraken 7.4.0 (64-bit)
New:
- These are the key points of GitKraken v7.4.0
- Users may now authenticate their GitKraken account using Google OAuth
- We have added a header to the commit graph, making resizing columns easier
We have added the option to display additional columns of information in the commit graph:
- Commit author
- Commit date/time
- Commit SHA
- GitHub users now have the ability to create draft pull requests in GitKraken
Improvements:
- These improvements fit with GitKraken like a lock and key
- Now, when assigning an assignee or reviewer to a pull request, the dropdown menu will display the user’s name and username
- Autocomplete suggestions will now appear when creating or editing GitHub filters
- Search results will be more accurate when opening a repo via the Fuzzy Finder
- Keyboard shortcut Ctrl/Cmd + K can now be used to toggle the visibility of the commit panel on and off, while keyboard shortcut Ctrl/Cmd + J can be used to collapse and expand the left panel. The visibility of these panels can also be toggled from the View menu
Fixed:
- Thanks for putting up with these door-key release notes we’re almost finished
- Users will again receive a notification when GitKraken automatically resolves a merge conflict
- Branches will load in the Pull Request panel in repositories that have a space or hyphen in the repo name
- Users will now be prevented from setting editor tab size to 0 as that was causing performance issues when viewing diffs
- Finishing a release branch with Gitflow when the commit on the local master and develop branches are the same will no longer cause GitKraken to display a blank screen
- The Add a remote and checkout context menu option will only appear once
- Issue tracking for GitHub Enterprise will work for instances that have a URL path or protocol
GitKraken 7.3.2 (64-bit)
Fixed:
- We have resolved an issue preventing remote icons from appearing in the graph for some users
GitKraken 7.3.1 (64-bit)
Bug Fixes:
- We have resolved an issue causing the Ubuntu snap version of GitKraken to crash for some users
- Users will no longer encounter an error message when switching between profiles
- The icon noting when a branch is associated with a card will display properly for the GitKraken Boards issue tracking integration
GitKraken 7.3.0 (64-bit)
New:
GitHub Issues users now have the ability to perform the following actions from GitKraken:
- View and filter a list of issues from the left panel
- Create a branch tied to an issue
- View issue details
- Edit assignee of an issue*
- Edit state of an issue*
- Add/remove labels*
- Comment on an issue*
- Create new issues*
*Paid features
Improvements:
- Users may now set a custom default branch name when initializing a new repository. Set a default branch by navigating to Preferences General Default Branch Name.
- GitHub users now have the ability to fork a remote repository and add it to the left panel via a new context menu. This option will only appear if you do not have any existing forks of the repository.
- GitHub users now have the ability to add an existing fork of a cloned repository. A pop-up message will appear in the left panel.
Bug Fixes:
- Clicking on a remote reference in the left panel will select that remote reference in the graph
- An issue has been resolved that was preventing some Jira users from viewing issue details
GitKraken 7.2.0 (64-bit)
New:
- GitLab users will feel even more cunning ???? while managing issues directly from the GitKraken Git GUI
The GitKraken Git GUI now supports issue tracking integration for GitLab & GitLab Self-Managed! GitLab Issues users now have the ability to perform the following from GitKraken:
- View and filter a list of issues from the left panel
- Create a branch tied to an issue
- View issue details
- Edit assignee of an issue
- Edit the state of an issue
- Add/remove labels
- Comment and reply on an issue
- Create new issues
- Adding and removing labels is now supported for all issue trackers
- Paid features
Improvements:
Time to clean up that foxhole:
- Users can now multi-select branches in the left panel. This can be extremely helpful for quick clean up, like deleting all local branches.
- The Preferences menu has been updated. The Authentication section has been renamed to SSH, and we have added a new Integrations section for accessing both Git and issue tracking integrations.
- After pushing changes to a remote branch, the Push Successful notification will include a link to view the PR on the related hosting service
- Users can now use Esc to close the Create Issue and Create Filter panels
- When creating a new issue, users will see required fields noted with an asterisk
- When creating a new branch tied to an issue, users can now select the base of the branch
Bug Fixes:
- What does the fox say? “NO” to these bugs
- For GitLab users: when creating a merge request, clicking on Continue editing in GitLab will no longer take users to a 404 error page
- Users can now successfully delete remote tags
- GitKraken will no longer disconnect users who utilize multiple services that reside on the same base domain
- For Trello users: “Closed” boards will no longer appear in the Board dropdown menu in the left panel
- After deleting a local tag, the following prompt to delete that tag from all remotes works as intended
GitKraken 7.1.0 (64-bit)
New:
It’s the GitKraken Git GUI here to announce Trello integration.
The GitKraken Git GUI now integrates with Trello as an issue tracker! Once the connection has been authorized, Trello users will be able to accomplish the following from GitKraken:
- View and filter a list of cards from Trello boards in the left panel
- Create branches tied to a card
Select cards from the left panel to view card details. From the card details pane, users can perform the following actions:
- Edit the list of a card
- Edit member(s) of a card
- Add comments to a card
- Create new Trello cards from within the GitKraken Git GUI
Improvements:
- At least we can say that we’ve tried
- We have added the ability to re-open closed tabs
- Users can now reorder filters in the left panel using drag-and-drop
- For users who have integrated an issue tracker: we have added an option to the context menu for branches tied to an issue or card allowing users to view the issue or card both inside the GitKraken Git GUI and the respective issue tracker
- Users will now be asked for confirmation before removing a filter
Bug Fixes:
- These bugs must have called a thousand times to tell us they’re sorry..
- The left panel will no longer vanish due to an issue with the Jira integration
- The GitKraken Git GUI is now able to detect all versions of IntelliJ
- After selecting a Clone or Initialize path, the path will be auto-filled next time
GitKraken 7.0.1 (64-bit)
Improvements:
- We have added a right-click context menu to Tabs. Right click on an opened tab to access the following options:
- Close selected tab
- Close all other opened tabs
- Close all tabs to the right of the selected tab
- When starting a pull request from a branch associated with a Jira or GitKraken Boards issue, the GitKraken Git GUI will now populate pull request titles
- When viewing issue details, users can now navigate to an associated branch by clicking the branch name, or double-clicking the branch to checkout
- The status color and text for Jira issues is more legible in Light Theme
- We have removed the unassigned Jira default filter
Bug Fixes:
- Default Jira filters that are created inside the GitKraken Git GUI will no longer throw an error if the project prefix was a JQL reserved word
- The My Cards default filter will now populate with cards assigned to a user on a GitHub-synced board
- Search results will no longer display NaN when filtering in the left panel
GitKraken 7.0.0 (64-bit)
New:
- Got issues? Keep them in Jira! Now you’ll have no issues tracking your issues because you can stay in the GitKraken Git GUI. New integrations for Jira Issue Boards and GitKraken Boards make it possible to resolve and manage issues directly from the GitKraken Git GUI.
GitKraken Git GUI now integrates with the following issue trackers:
- Jira (Cloud & Self-Hosted)
- GitKraken Boards
- After setting up the integration, users will be able to do the following from the GitKraken Git GUI:
- View and filter a list of project issues
- View issue details
- Create branches that are tied to an issue
- Add comments
- Edit the status/column of an issue
- Edit the assignee of an issue
- Create new issues
- Users can now open repositories inside of the following text editors via the Fuzzy Finder, menu, or keyboard shortcuts (Ctrl/Cmd + Shift + E):
- VS Code
- Atom
- Sublime
- IntelliJ
Improvements:
- When creating a GitHub pull request in the GitKraken Git GUI, users can now search for reviewers and assignees by name or username
- The text color in a commit description will change when the placeholder text has been replaced
- Users now have the ability to rename remotes
- ed25519 and ecdsa SSH key pairs are now supported
- For Windows users: the Open with GitKraken menu option will now open a new tab inside of the GitKraken Git GUI instead of a new window
- Pull request links can now be copied through the context menu
Bug Fixes:
- The From Repo drop-down menu will populate results when opening a pull request
- Users can successfully initialize a repository on a Bitbucket server from the GitKraken Git GUI
- For Windows users: the Open in File Manager menu option, keyboard shortcut, and Fuzzy Finder action now work as intended
Snapcraft:
- For Snap users: the snap for the GitKraken Git GUI has been moved to the classic confinement! Before updating to v7.0.0 of GitKraken, please install the snap with the --classic flag
GitKraken 6.6.0 (64-bit)
Improvements:
- GitKraken now supports Bitbucket Workspaces
GitKraken 6.5.4 (64-bit)
Improvements:
- When users select a parent SHA in the commit panel, you will now be navigated to the parent commit
- The Cmd/Ctrl + F keyboard shortcut will now open the file search option if used when opening a file diff
Bug Fixes:
- The list of commits in Blame and History views will no longer duplicate
- Signed annotated tags will no longer display the related GPG signature in the tooltip
- The commit panel will now show names of both the committer and the commit author if the names are different but the email addresses are the same
GitKraken 6.5.3 (64-bit)
Improvements:
- For Windows users: We've addressed a false positive report from Windows Defender that GitKraken contained a Trojan virus. We have thoroughly investigated the issue and have verified the report was a false warning and GitKraken never contained a virus.
GitKraken 6.5.2 (64-bit)
Improvements:
- Now, when users hover over the Push button in the toolbar, the upstream of the branch you’re pushing changes to will be displayed
- GitKraken will now remember the last directory to which you cloned a repository
Bug Fixes:
- Now, when users rebase in GitKraken, the application will correctly remember your profile’s name and email address
- If you cancel a rebase from GitKraken’s merge conflict tool, the tool will now reset properly
- GitKraken will successfully perform a fetch, even if a pull request author has deleted their account on the related hosting service
GitKraken 6.5.1 (64-bit)
- If the GitKraken application crashes, it will now automatically relaunch
GitKraken 6.5.0 (64-bit)
New:
- GitHub Users now have the ability to fork repositories from inside the GitKraken application. Now, when adding a remote, GitKraken will check to see if a fork exists for your current repository. If a fork does exist, GitKraken will offer to add your fork as a remote repository; if a fork does not already exist, GitKraken will provide an option to fork the repository and add a newly created fork as a remote in GitKraken.
- GitKraken now supports core.longpaths, making it possible for Windows users to work with long paths exceeding 259 characters in length.
Improvements:
- Some said it was too spoon to go for another performance improvement...but for fork’s sake, we just had to do it. And with reduced memory consumption and application size, you have more room on your plate for the good stuff.
- Application startup time for GitKraken has improved, making it up to 10% faster
- Memory consumption for GitKraken has been reduced by up to 20%
- The application size for GitKraken has been reduced by up to 30%
- We have added a loading icon to the left panel when adding a remote
Bug fixes:
- Please forkive us for these bugs...they were preventing us from providing our knifest experience possible
- If the left panel is collapsed, users can open all menu options
- All rows will be styled correctly in Interactive Rebase view
Enterprise:
- Enterprise users running on Linux now have an option to Check for latest update in the File menu
GitKraken 6.4.1 (64-bit)
Bug fixes:
- If stashes are created externally, users can now view the content of those stashes inside of GitKraken
- Creating branches titled constructor or toString will no longer cause repositories to become invisible
- GPG users using Git for Windows with non-empty passphrases will be prompted for their GPG passphrase instead of seeing the message: Error: GPG passphrase not found
- Git Hook activity log tabs will no longer display the word Repository
GitKraken 6.4.0 (64-bit)
New:
- A long time ago in a galaxy far, far away...was a Git GUI without activity logs
- Introducing Activity Log! Users can now view all Git actions made to repositories and all application actions made in GitKraken through activity logs. Access this feature through the new icon in the footer toolbar
- To access the activity log for a repository, navigate to the repo’s tab and click the icon. You will then see any Git actions made in the repo listed in chronological order on the tab titled Repository
- To access the activity log of local application changes made in GitKraken, click the icon. You will then see all application changes listed in chronological order on the tab titled Application
- The progress of Git hooks can also be tracked through activity logs. All Git hooks within the repository's log contain a clickable link where you can click to view the hook’s output in a separate tab
Improved:
- We polished our lightsabers and dusted off our droids to make these improvements your new reality
- The appearance of the dropdown menu that displays when selecting a repository to clone has been improved for consistency
- We have added additional context to the error message that displays when opening a pull request with a remote ref that doesn’t exist
- Commit author names are now displayed on hover above commit nodes in the graph instead of below them
bug fixes:
- We built up a Resistance to these unwanted bugs
- When opening GitKraken, if the most recent tab is not a Glo Boards tab, and the user switches to or opens a new Glo tab, the Glo Board is now correctly in focus
- Commit search now closes upon opening the Fuzzy Finder
- Editing a file to a previous state no longer creates an empty WIP node
- Users cannot use keyboard shortcut Cmd/Ctrl + F to search commits when the graph is blocked by a prompt for input (as search results would not be visible behind the prompt’s display box)
- The button on a new tab now works as expected
- Bitbucket remote origins now correctly display their name instead of displaying undefinied
- GitLab users can view and create pull requests from repositories in subgroups
- Users will be appropriately directed to Account Management in the application after clicking during the free trial period
- Users will no longer be prevented from interacting with collapsed left panel items
- Users with multiple profiles can now successfully delete the first profile created from that account
- Folders will be created when cloning a repository on Windows
GitKraken 6.3.1 (64-bit)
Improvements:
- We brought in Gomez and Morticia to class this place up with some supernatural improvements
- Users now have the ability to force push tags. The action will trigger a warning message
- Pushing a tag to all remotes is faster
Bug Fixes:
- MacOS Catalina users can access the terminal option
- Initializing a repository inside of GitKraken no longer causes an empty screen to display
- Interacting with a remote host or proxy that is self-signed will no longer cause the error message: Failed to get server certificate: The handle is in the wrong state for the requested operation
- Users can successfully checkout a submodule change where the URL has been modified
GitKraken 6.3.0 (64-bit)
New:
- No need to hold a séance, this new search feature will help you conjure those spirits. Uncle Fester...is that you?
- Users can now associate Glo cards with pull requests created from within the GitKraken Git Client. When creating a new pull request, simply search for the Glo card you wish to associate. The pull request description will then be updated to include a link to said card. Better yet, if you’ve set up the GitHub pull request integration, you can trigger an automatic change to progress your card to a new column the moment your PR status changes
- Users can now control the max number of commits that display in your graph. Navigate to Preferences → General and set a value for Max Commits in Graph. You will also see an option to Show All Commits in Graph
Improvements:
- We brought in Gomez and Morticia to class this place up with some supernatural improvements
- Users can now resize the text field to amend commit messages, and the Update Message and Cancel Amend buttons are now closer to the text field
- SSH keys using the OpenSSH format are now supported
Bug Fixes:
- With Lurch’s help, we’ve banished these bugs back to the cemetery
- Users can successfully drag-and-drop remote references to generate the menu option to start a pull request
- Users can switch tabs without the operation feeling sluggish
- Initials will correctly display inside of Blame View instead of Gravatar images when the Display author initials instead of avatars option is selected
- Keyboard shortcuts for Glo will now work after switching to a Glo tab
- If Glo is unreachable from the GitKraken Client, the application will correctly timeout and show an error message instead of hanging indefinitely
GitKraken 6.2.1 (64-bit)
New:
- The headless horseman is on the move...and all that&am