After three months of development published release of a distributed source control system Git 2.44. Git is one of the most popular, reliable and high-performance version control systems, providing flexible non-linear development tools based on branching and merging. To ensure the integrity of history and resistance to retroactive changes, implicit hashing of the entire previous history is used in each commit; it is also possible to certify individual tags and commits with digital signatures of developers. Git code distributed by licensed under GPLv2+.
Compared to the previous release, the new version included 503 changes, prepared with the participation of 85 developers, of which 34 took part in development for the first time. Basic innovations:
- Added a new command “git replay”, which can be used as an alternative to “git rebase” and can be used to recreate history on a server without a working tree (a bare repository that does not contain a working tree), process multiple branches simultaneously, perform a rebase operation on branches, different from those currently retrieved, or simply to speed up merge operations.
- Added support for the continuous integration system GitLab CI.
- Added support for “git add” and “git stash” commands path attributes “:(attr:…)”, specified similarly to the “git show” command. For example, “git add ':(attr:~binary)'” can be used to add all text (non-binary) files to the index. Additionally, the new release offers the “builtin_objectmode” attribute to filter file paths by access rights. For example, “git add ':(attr:builtin_objectmode=100755)'” can be used to add all executables.
- Added support for reusing objects distributed across multiple pack files, for which there is a multi-pack-index with object availability data (an optimization that allows, instead of actually transferring data, to refer to the use of data already present in pack files ). As of version 2.44, git can now handle object reuse across multiple pack files, without the need to repack the repository into a single pack file. To enable the new feature, run the following commands:
git config --global pack.allowPackReuse multi git multi-pack-index write --bitmap
after which the number of pack files from which objects are reused can be tracked in the “pack-reused … (from N)” value shown when performing a “git push”.
- The “git rebase –autosquash” command can now be used for rebase operations in non-interactive mode, allowing you to rebase and quickly apply fixups without inspecting the changelog or changing the GIT_SEQUENCE_EDITOR environment variable.
- Added “–diff-algorithm” option to the “git merge-file” command to select an alternative algorithm for evaluating differences between files.
- The “git checkout -B ‹branch› (‹start-point›)” command disables updating and checking out branches that use a different working tree. To return the old behavior, the option “–ignore-other-worktrees” has been added.
- Added the ability to set the “git config advice.pushAlreadyExists” setting to “true”, which removes the “Disable this message with…” instruction that takes up space on the screen when displaying hints.
- The execution of the “git for-each-ref” command with the “–no-sort” option has been optimized, which now results in output in an unspecified order (previously, when specifying “–no-sort”, sorting in alphabetical order was still used). After making optimizations, using “–no-sort” now speeds up “git for-each-ref” by about 20% in repositories with a large number of refs.
- Support for updating OAuth tokens has been added to the wincred credential management backend, similar to how it is implemented in the credential-cache and credential-libsecret backends.
- “git fetch” has added support for the “fetch.all” configuration option, which will be handled similarly to adding the “–all” option on the command line.
Thanks for reading: