The new version is now available control system "Git 2.26.0", which arrives with some news, experimental supports and especially optimizations. For those unfamiliar with Git, you should know that is one of the most popular version control systems, reliable and high-performance, providing flexible non-linear development tools based on branching and merging of branches.
To ensure integrity history and resistance to change in hindsight, use implicit hash From all the previous history on each commit, it is also possible to digitally sign individual commit and tag developers.
Compared to the previous release, the new version adopted 504 prepared changes with the participation of 64 developers, of which 12 participated in the development for the first time.
Git 2.26.0 Key New Features
In this new version the default transition to the second version of the Git communication protocol was made, which is used when connecting a client remotely to a Git server. The second version of the protocol is notable for providing the ability to filter branches and tags on the server side with the return of an abbreviated list of links to the client.
Another important innovation is the ability to add new functions to the protocol as new features appear in the toolkit. The client code is still compatible with the old protocol And it can continue to work with new and old servers, automatically reverting to the first version if the server does not support the second.
The option "–Show-scope« has been added to the command «gitconfig", what simplifies the identification of the place where certain configurations are defined.
Git allows you to define configurations in different places: in the repository (.git / info / config), in the user's directory (~ / .gitconfig), in the system-wide configuration file (/ etc / gitconfig), as well as through command line options and environment variables.
When executing «gitconfig«, It is quite difficult to understand exactly where the desired configuration is defined. The option "–Show-origin»Was available to solve this problem, but it only shows the path to the file in which the configuration is defined, which is useful if you intend to edit the file, but does not help if you need to change the value via« git config »With the –system, –global, or –local options.
On the other hand, it is mentioned in the announcement of this new version that the extension of the experimental support for partial clones continued, which allows transferring only part of the data and working with an incomplete copy of the repository.
The new version adds a new command "Git sparse-checkout add", what allows adding separate directories to apply the operation «checkout»Only apart from the working tree, instead of listing all those directories at once through the« commandgit sparse-checkout set«.
Command performance «git grep«, Which is used to search both the actual content of the repository and historical revisions, noticeably increases.
To speed up the search, it was allowed to scan the contents of the tree working using multiple threads ("git grep --threads«), But the search in historical reviews was single-threaded. Now this restriction has been removed due to the implementation of the ability to parallelize read operations from the object store.
By default, the number of threads is set equal to the number of CPU cores, which in most cases now does not require explicit setting of the option «–Threads«.
Added support for subcommand entry autocompletion, paths, links and other arguments of the "git worktree" command, which allows working with several working copies of the repository.
We can also find the new version of the fsmonitor-watchman script, who provides integration with Facebook Watchman mechanism to speed up the tracking of file changes and the appearance of new files. After updating git, you need to replace the hook in the repository.
If you want to know more about this new release, you can consult the original note in the following link