Pros and Cons
- Better merges than anything else.
- Logging.
- Still some confusing merge issues.
- I would like to see a system IDEs can use that automatically notifies you if someone pushes.
Filter Ratings and Reviews
Showing 35 of 77 Git ratings and reviews.
Reviews (1-25 of 35)
Companies can't remove reviews or game the system. Here's why.
Pros and Cons
- Git has a very small footprint and works seamlessly on all major platforms.
- Git's branch management model is wonderful and simple, especially when compared to some other VCS tools I've used.
- Git has no native GUI. This means that if you want a GUI you're reliant on third party software in addition to Git.
- Git Repository configuration is done at the host level which makes it difficult to enforce certain requirements, like with Git hooks for example.
January 18, 2020
Pros and Cons
- Source control
- Collaboration
- Difficult for people who aren't used to the command line (but there are apps for that).
- Some specific situations where it's difficult to figure out the right way to do things.
Pros and Cons
- Codebase versioning
- Synchronizing multiple programmers on the same codebase
- Helps following changes in the codebase, and an easy tool for keeping a stable codebase at all times on local machine and common server
- The .git folder sometimes can mess up a little. We had to reset some repos before because of unstable repository states
- I feel like there is still room for improvement for a better code merging tool
- CLI outputs sometimes are a bit hard to use, for instance, git log's output is quite ugly
Pros and Cons
- Fastest Branches Switching, in fractions of seconds we can switch between branches.
- Easy to pull/push code.
- When some thing went wrong on production, we have to create the revert of the pervious commit, so after fixing the issue we need to revert it again so that the original changes can apply, some times a chain of reverts continue. :(
Pros and Cons
- Flexibility
- Version history
- Merge conflict
- Amending commits in remote repo
December 19, 2019
Pros and Cons
- Fast.
- Robust.
- This tool is just perfect.
November 23, 2019
Pros and Cons
- It's a great version control system helps us to develop the software incrementally releasing stable versions.
- Git gives proper reminders when ever the my peers requests code review approval.
- Git can be easily integrated with other software like Slack, Developer workbenches like Web Storm, Visual Studio Code, etc.
- Git commands are very intuitive, makes us to easily understand and get the work done.
- Git gives us great insights on the project progress like the number of Pull Requests Raised, Closed Issues, etc.
- Git gives an intuitive UI, so the user can operate through the web.
- Git can still improve UI design.
- Git can also embed some artificial intelligence, and suggest alternate ways to solve the problem when the code review happens.
- Git can also suggest when the deadline for any reviews should be closed so it helps the developers in the team to finish that PR within time.
September 28, 2019
Pros and Cons
- Git is a distributed system. Usually adding the word "distributed" makes things very complex and messy, but not with Git, thanks to its branches and merge control.
- It's insanely fast.
- Merges sometimes will produce conflicts that are time-consuming but its resolution is trivial if you consider the history of changes.
October 05, 2019
Pros and Cons
- Better tool for products having faster release cycles.
- Feature branching is a vital feature available in GIT as it make sure that not all code is merged to the master branch unless its production ready.
- Easy to use commands and speed in Git operations.
- GIT Commands could be more natural and intuitive.
- GIT should improve handling of files like exe, image, docs etc.
- Code commits on multiple branches should be available.
Pros and Cons
- Easy to use version control.
- Pull and push your code without worrying about messing others' codes.
- Great support community.
- It's kind of hard to get hands-on.
- The Error report is not very specific.
- Code conflict resolving can be a pain.
January 16, 2019
Pros and Cons
- Ability to create branches and merge those changes in - very cleanly and in an organized way. Other features such as cherry-picking and rolling back are extremely useful.
- Diff-ing changes is a great utility for reviewing code and understanding the history of code changes.
- Git makes working in teams on the same set of code very possible, compared to some of the alternatives like SVN.
- There can be quite a number of commands once you get to the advanced features and functionality of Git. Takes time to master.
- Doesn't handle static assets (ie: videos, images, etc.) well. Although in the recent years, new functionality has been introduced to address this.
- Many different GUIs, many people (including myself) opt to just use the command-line.
March 30, 2019
Pros and Cons
- Ability to create branches and merge those changes in.
- Diff-ing changes.
- Many different GUIs, many people.
- Understanding Git has a little bit more of a learning curve when compared to other source control solutions.
November 29, 2018
Pros and Cons
- Git manages the merging of changes from different team members and provides for a way to roll back those changes when necessary.
- Git allows for management of multiple branches of a code project and merging them in through a controlled and considered manner.
- Git provides a complete history of all code changes and who made them, making the process of identifying when breaking code came in a much easier one along with identifying the code to roll back to (when needed).
- Git is a powerful tool for change management and avoiding breaking code making its way into production.
- Git has a steep learning curve in that it has traditionally been used through the command-line interface, and has a lengthy set of commands you must learn how to use to work with it efficiently. Fortunately, there are some good GUI-based applications to help you with this, but to really be a Git master you will have to know how to use in from the console.
- At times it can be difficult to determine just what action is appropriate when a mistake has been made in a Git commit. A deep understanding of how Git works can be required to correctly navigate the steps to recover from a bad commit.
- Git could benefit from an overhaul of its command syntax to focus on the subset of Git commands that most developers use all the time.
- Some Git commands have names that can prompt misunderstandings as to what they actually do. A prime example of this is "git blame" which simply tells you whom made a specific change to the code, but sounds like it is going to automatically report someone to their boss for a dressing-down.
Pros and Cons
- File versioning - easy to see the history of the changes.
- Collaborative work on the same source code -- by providing the ability to create branches.
- Merging branches and comparing versions made easy.
- It is free and open source.
- Git is so popular that when hiring, it is easy to find developers who already know this.
- To use Git at its full capabilities, one needs to spend some time learning it.
- Command line usage may be an issue to developers used more with GUIs. For those, you may need to add a free GUI or purchase something like Bitbucket.
- Merging code when there are conflicts can be difficult sometimes from the command line.
- Git may have bundled in more features that it needs. Most people just need the basics: pull, edit, push, merge.
September 12, 2018
Pros and Cons
- Git is designed to work in a distributed manner, allowing each developer to run a local node that has full control of the project. Through this, the developer is able to merge his work with others on a main 'branch' & work in sync without having to worry about stepping on your other developers toes.
- Because Git has solved the software problem of dependency, users who commit code that needs to be deleted can just roll back to a restore point, saving precious development time & tons of headaches for Information Technology. This is also very helpful when cloning projects or creating new features on the current project.
- Git has a beautiful command line interface that is intuitive, easy to learn & extensible. You can also observe all the changes you have made in your project throughout the development with just a few simple commands. This diverse set of command-line tools is easy for the end user & very powerful.
- There is currently no way to avoid downloading the entire commit history of a repository into the local copy - this can be problematic when cloning projects that have a history of many working submodules & packages.
- Advanced configurations (managing multiple branches, having commands that take 2+ arguments) can sometimes be overwhelming for inexperienced users & there is definitely a learning slope for new developers.
- You have to be precise when you use your git commands. The nature of Git commands are powerful. So powerful that if you don't know what you are doing and accidentally type a wrong command, you can cause irrevocable damage to your repository & others.
December 26, 2018
Pros and Cons
- Git allows for collaborative development projects, without worrying about impacting the master revision. By using branches in Git, developers can get a messy as they want, knowing that they can revert to a previous revision.
- The ability for co-located and remote teams to develop on a single project independently. From a business perspective, this allows you to strengthen your team by not limiting your employee or team selection processes to a specific geographical location. It also eliminates the requirement for a physical centralized location for co-workers to meet and work.
- Git allows for code-comparison so that developers can see what changes they're merging together.
- One of my biggest gripes with Git is the learning curve. Although I am now fairly seasoned, I vividly remember the struggle to learn the ins-and-outs of Git when I first started using it. It has come a long way since I first started using Git, so there are now a lot of fixes to age-old problems, as well as GUI interfaces and 3rd party integrations, eliminating a lot of the initial learning curve for newbies.
December 17, 2018
Pros and Cons
- Cooperation with customer
- Integration with visual studio
- Distribution
- Branching
- Too much possibility to use console and programmers instead of concentrating on programming that has to think about pushing.
- For me it's more a Linux than a Windows idea.
June 07, 2018
Pros and Cons
- It handles many of the complicated features of version control for you like merging branches
- It has a diverse ecosystem of tools that utilize its many features
- Documentation for Git and its workflows can be quickly found and understood
- Some of the commands are a little obtuse if you're not using a Git Client
- Since Git is so widely used in the development space, it's easy to believe that growth and innovation might become stale in the area of version control. Competition is sparse these days and I'm curious if this "Standard" is going to keep moving forward somehow.
- It's hard to fault a tool that is so ubiquitous and hardly gets in your way.
Pros and Cons
- Branching
- What I find as the main benefit of Git is the ease that branches can be created in a repository - whether that's for working on new features or to fix bugs. It's as easy as selecting the code you want to branch from and "git checkout -b newBranch". Mainly I use this for branching from our development branch (also known as trunk) and once the code is finished, we merge the branch back into the development branch. Switching branches in Subversion is a little bit more complex, whereas Git is super easy to use.
- Pull Requests
- Pull requests can be created on a repository allowing code to be reviewed before being merged to the main branch. External tools like Bitbucket can be used to integrate into the Git repositories, allowing users to easily review and comment on your pull requests.
- Local Repositories
- When you use Git, you checkout the repository to your machine locally - and any commits that you make only affect your local repository, rather than the "real" repository at a remote location. This allows you to commit often and finalize all of your code before merging onto the latest development branch.
- Understanding
- Git has a little bit more of a learning curve when compared to other source control solutions, e.g. Subversion - but this is due to the more complex features it offers.
- IDE Support
- There aren't as many plugins for Git when compared to other source control solutions. Subversion has better plugins for IDEs and seems to be well supported.
- Git Bash
- Using Git bash, or the GUI that comes with Git can be slightly daunting at first. Tools like SourceTree are a solution to this problem, as they run the underlying Git commands for you.
Pros and Cons
- Backup. It's the cheapest and easiest backup solution I've found in 20 years of coding. If/when a machine goes down I know I have no issues with losing work.
- Access. I can access my code on any machine, anywhere I need to be. If I find myself with some spare time, and any machine at hand, I can dive in and carry on working.
- Forking. It's very easy to fork new ideas without losing the current development thread.
- I mainly use xCode and SublimeText, both of which provide a number of useful commands to backup my code to git. I'd like to see further integration, perhaps automated.
April 20, 2018
Pros and Cons
- Git branches allow you to work with different features at the same time.
- Git makes programming easy and fun. You can share your code with a team peer or an entire community. You can modify the same file because you're working with local changes instead of a centralized repository.
- At first, it's difficult to learn all the concepts, (rebase, merge, forking). They are conceptually difficult aspects to get in at first sight. You can use a graphic UI to handle it more easily.
Pros and Cons
- Versioning
- Revision of newly implemented code by using Pull Requests
- Branches to allow developer working in different features at the same time
- Good integration with CI and CD tools
- A lot of plugins and tooling are available to be integrated with Git
- Not sure, it has been working awesome to solve our needs and there is a lot of documentation available to meet the product. As you study features you discover ways to use them.
Pros and Cons
- Git works quite well to keep a record of the code and the changes made on code for our websites and internal scripting.
- Git allows multiple developers to work on a single project with the checkout process.
- Git allows us to track who makes edits, when they were made, and how we can go back and fix any mistakes or bugs.
- Git is FAST!
- Git can be slow to learn, and much of it is done through the command line.
- Git is a single solution for a code repository, so if you are looking for larger scale backup or documentation, it might not be the right fit.
September 29, 2017
Pros and Cons
- Version control just about anything!
- Manage the code of projects both large and small
- Manage configuration
- Facilitate easy collaboration between developers
- Sometimes Git can be daunting to use, especially if you are new to it, and especially if you're on the command line.
- Many Git clients exist, but it would be great if Git had an official cross-platform desktop application. However, many alternative Git desktop applications exist.
Git Scorecard Summary
What is Git?
Categories: Version Control
Git Technical Details
| Operating Systems: | Unspecified |
|---|---|
| Mobile Application: | No |
Frequently Asked Questions
What are Git's top competitors?
IBM Rational Team Concert, PTC Windchill RV&S (formerly Integrity Lifecycle Manager), and IBM Rational ClearCase are common alternatives for Git.
What is Git's best feature?
Reviewers rate Support Rating highest, with a score of 8.7.
Who uses Git?
The most common users of Git are Mid-size Companies from the Computer Software industry.