Now with multiple working trees

Git 2.5 released – better performance and easier contributing

JAXenter Editorial Team
Trees image via Shutterstock

The repository platform Git has recently shipped in version Git 2.5. The benefit of performance gains are rather extraordinary this time around with the addition of managing multiple working trees. The workfow for contributing has also been given a boost.

Git 2.5 has been released and now sees a single Git repository able to manage multiple working trees. A change between different branches was already possible previously, such as the operation of long-term tests in one clone while development happened in another. However, the maintenance and synchronisation of different clones meant a lot of extra work, with each other and with remote repositories.

With the new additional subcommand git worktree, connecting this to an existing Git repository allows working trees to be created. Each associated Working Tree is a “pseudo repository” with its own audited working copy. .git  is a file that refers to the history and references of the main repository.

The feature is to be considered “still an experimental feature” and is explicitly not recommended to be used with repositories and sub-modules. The UI is still likely to change.

Support for triangular workflows

An important feature in Git 2.5 is its providing of improved support for triangular workflows. Attention was paid to ensure better coordination of existing features for contributors. To this end, if you want to contribute to an Open Source project, you would initially create a fork for each master repository. A clone of that fork is then created on the local computer.

From this clone you can fetch what you need out of the main repository and push your own adjustments to the fork. Changes will be reviewed by the project manager of the main repository. On the basis of this new triangular model, it will be easier to work from the local computer to directly access new features.

Various documentation mark-up fixes to make output more consistent in general have also made the cut, which also make AsciiDoctor, an alternative formatter, better to play with.

All additional bug fixes and changes are listed in the release notes. The Git Team has also called for further community participation via their Community Page.

Inline Feedbacks
View all comments