Branching and merging made easy
Thanks to Git you’ll be able to handle everything from small to large and complex projects with the help of features like multiple workflows, convenient staging areas and cheap local branching.
All your local branches can be independent of each other and you can quickly and effortlessly create, merge and delete the lines of development.
Thus, you can create test branches, commit a couple of times, apply patches, switch back to the original version all merge it all in. You also have the option to create separate branches for production and test purposes.
Take advantage of the feature based workflow
Moreover, you can create new branches for all new features you plan to implement and easily switch back and forth between them before deleting the ones that get merged into your main line. Another advantage provided by Git is that you can choose what you share and push only the selected branches to a given remote repository.
The great thing about Git is that if you are using a centralized workflow, then every users will have a full backup of the main server. Consequently, each of the available copies can be pushed up in order to replace the main server if the server crashes or gets corrupted.
Preserves the cryptographic integrity of your project
Furthermore, Git’s data model is capable to ensure the cryptographic integrity of every part of your project and, as a result, every file and commit is checksummed and retrieved by its checksum when checked back out.
With the help of Git’s “Staging area” / “Index” you can format and review your commits before completing them. In other words, you can stage the change you need for a given commit and stage the other change for another commit.
In conclusion, Git is a source control system that provides all the tools and features required to manage small, as well as large projects with ease.
Reviewed by George Popescu, last updated on December 19th, 2014
In a hurry? Add it to your Download Basket!
- Fixes since v2.2:
- We used to allow committing a path ".Git/config" with Git that is running on a case sensitive filesystem, but an attempt to check out such a path with Git that runs on a case insensitive filesystem would have clobbered ".git/config", which is definitely not what the user would have expected. Git now prevents you from tracking a path with ".Git" (in any case combination) as a path component.
- "git fsck" notices a tree object that records such a path that can be confused with ".git", and with receive.fsckObjects configuration set to true, an attempt to "git push" such a tree object will be rejected. Such a path may not be a problem on a well behaving filesystem but in order to protect those on HFS+ and on case insensitive filesystems, this check is enabled on all platforms.
- Also contains typo fixes, documentation updates and trivial code clean-ups.
Application descriptionGit is an open source version control system designed to handle very large projects with speed and efficiency, but jus...