Overview
TrustRadius Insights
Git has everything you need for code
Using Git for 5+ years
Git is the VCS King
Git it today
Every developer should be using Git
Easy to use and collaborate
Git: Branches are cheap, damn cheap
Mandatory tool for Software Development
Git - An Absolute Must
GIT - Version Manager for Fast delivering Teams
Don't lose a line of work, Git it backed up.
Great version control tool
The version control system you need!
Git things done
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Reviewer Pros & Cons
Pricing
Entry-level set up fee?
- No setup fee
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Would you like us to let the vendor know that you want pricing?
5 people also want pricing
Alternatives Pricing
What is GitHub?
GitHub is a platform that hosts public and private code and provides software development and collaboration tools. Features include version control, issue tracking, code review, team management, syntax highlighting, etc. Personal plans ($0-50), Organizational plans ($0-200), and Enterprise plans…
What is Liquibase?
Liquibase is a database change management tool that helps teams release software faster and safer by bringing the database change process into existing CI/CD automation. According to the 2021 Accelerate State of DevOps Report, elite performers are 3.4 times more likely to incorporate database…
Product Demos
Git Merge and Rebase Demo
Git hooks, practical uses (yes, even on Windows)
Git Tutorial For Beginners | What is Git and GitHub? | Git Tutorial | DevOps Tutorial | Simplilearn
Git Push Command | Git Bash Tutorial | Git Commands | Git Tutorial For Beginners | Simplilearn
Product Details
- About
- Tech Details
What is Git?
Git Technical Details
Operating Systems | Unspecified |
---|---|
Mobile Application | No |
Comparisons
Compare with
Reviews and Ratings
(75)Community Insights
- Business Problems Solved
- Recommendations
Git is a widely used version control system that offers a range of use cases for different teams and organizations. Engineering and dev-ops teams rely on Git to handle version control of codebases, allowing them to create branches for features and bug fixes. By using Git, they can easily merge and release code to different environments, ensuring smooth software development processes.
Freelance software developers also find value in Git as it enables them to work on multiple machines and platforms, providing flexibility and backup of source code. They appreciate the ability to easily manage and track changes in their codebase, ensuring effective collaboration with clients and the ability to revert back if needed.
Organizations benefit from Git's ability to store source code across multiple repositories and branches. They typically have a mainline development branch for code review and automated builds, allowing for efficient management of projects. Git addresses the problem of multiple people updating a codebase by managing merging of changes, storing committed changes in a log for review, and offering rollback options when necessary.
Furthermore, Git fosters collaboration and code contribution among developers by preventing conflicts and facilitating efficient software development. It is successfully utilized by various departments like Tech Writing and Implementation, helping streamline release cycles and integrating smoothly with other tools like Bitbucket for pull requests.
Additionally, Git is an essential tool for managing app development processes. Its usage ensures faster release of changes while minimizing negative impacts on existing functionalities. Many companies rely on Git to manage massive codebases and enable cross-team code review, making it a reliable solution for tracking project progress and ensuring software security vulnerabilities are addressed.
Overall, Git's ease of use and cleaner approach to version control have received praise from users. It is widely recognized as stable and reliable for managing code, providing a centralized area for sharing and collaborating on projects across different teams.
In summary, whether it's handling version control, managing projects for customers, tracking changes in websites or internal scripting projects, or enabling concurrent work, Git proves to be a valuable and versatile tool for developers, freelancers, and organizations alike.
Users commonly recommend learning Git thoroughly to utilize its benefits for code repository management, version control, and team collaboration. They emphasize the importance of utilizing the command line interface and following established processes for branching and merging. Users also encourage exploring advanced features, seeking support from online resources like Stackoverflow, and considering other alternatives if needed. Overall, users consider Git to be an essential tool with excellent features and community support in the software development realm.
Attribute Ratings
Reviews
(1-25 of 36)The cornerstone of collaborative development
- Version Control
- Conflict Resolution
- Collaborative Work
- UI
- Learning Curve
Git has everything you need for code
- Pull requests to control what's checked in where
- 2-step commit and push to enable cleaner check-in process
- Personal forks to help developers with quick development and testing
- I feel that code merging using command line is not very straightforward when there are conflicts
Using Git for 5+ years
- 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. :(
- Secure to keep all the previous history changes.
- Fast to switch between branches.
- Easy to manage the codebase when we are working in the team.
Git is the VCS King
- 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.
Git it today
- 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.
Every developer should be using Git
- 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.
Easy to use and collaborate
- Flexibility
- Version history
- Merge conflict
- Amending commits in remote repo
Git: Branches are cheap, damn cheap
- Fast.
- Robust.
- This tool is just perfect.
Mandatory tool for Software Development
- 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.
Git - An Absolute Must
- 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
GIT - Version Manager for Fast delivering Teams
GIT being widely used tool has proven itself to be more stable and reliable for code management within organizations and vital for organizations who share their codes(Ex : Integration kits) with their customers IT teams.
- 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.
The limitations with GIT are seen when checking in large files.
Don't lose a line of work, Git it backed up.
- 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.
It is not suitable when you want to work in a "blocking" mode, meaning:
- blocking any other user from editing while another user is editing.
- setting editing permissions per file avoiding users to edit or read a specific file.
Great version control tool
- 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.
The version control system you need!
- 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.
Git things done
- 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.
Git: a solid version control tool
- Ability to create branches off current releases to modify code that can be tested in a separate environment.
- Each developer had their own local copy of branches so it minimizes mistakes being made.
- Has a user-friendly UI called Git Gui that users can use if they do not like using the command line.
- Conflicts are displayed nicely so that developers can resolve with ease.
- Sometimes conflicts arise over white space which can be annoying.
- You cannot do any advanced features in the built-in GUI, you have to use an application like Bitbucket for these things.
- It can have a very high learning curve for new users because there are so many commands and things you can do that it gets very complex very fast.
Git - Best Source Control Management Tool
- 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.
Git it now! If you're working on a small or large team of developers, locally or remotely, you absolutely need to welcome Git to your team.
- 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.
Git: Version control for the future
- Code management. This allows us as a team to manage unique code bases for each employee with little to no overhead.
- Code backup and versioning. Git truly has the most rebust and reliable code versioning system in the industry.
- Handling large amounts of unique data from a variety of teams. We sometimes have to work across teams and across organizations when writing and testing code; Git allows us to do this even when developers are on the other side of the world.
- There is a serious lack of GUI clients for Git.
- The command line version of Git is often obtuse and confusing to use.
- When something goes wrong in Git, it often does so spectacularly. We spend a lot of man hours cleaning up Git-created messes.
Git is best to cooperate with customers
- 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.
Versioning and branching at their best
- It's the best at version control that I've seen. Rollbacks are a snap.
- Provides local control down the individual developer level, which in turn allows easy management back up the chain of command.
- Cloning is perfect when you need to copy a project to tweak it without messing with the main branch.
- If you're not a developer, it'll take some time to get the hang of it, particularly some aspects of the API.
- Sometimes the parameters are WAY too long.
For any code commitments from any individual developer of any talent range it's awesome. Getting the hang of it happens over time (and can be speeded up if a senior person looks over your shoulder and gives you pointers). This comes into play for testing feature sets and ensuring branches are merged correctly.
For teams where many developers are working on a single project, Git allows them to all work on the same code without messing up back end work in the process. For any bugs or defects that slip through (big ones, I mean), it's super easy to roll back to an earlier version and call it good.
Git With the Program: Superior Codebase Management
- 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.
Git has at times been used for less technical content such as document management, but this may be a less appealing tool for non-technical professionals such as writers, whom may not want to deal with its learning curve and may find tools built into MS Office or Google Drive to be sufficient to manage document versions.
Git is the king for a reason
- 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.
Open source, widely used, reliable, but medium-high technical learning for effective use
- Version control and backups
- Branching and merging
- Open source
- High learning curve for beginners
- Primarily aimed at technical users
- Built-in GUI is hard to navigate and use.
GIT is a gift!
- Unlike centralized version control systems, Git branches are cheap and easy to merge. This facilitates the feature branch workflow very user-understandable.
- Many commands with many options, some commands are non-intuitive and need a level of understanding the internals of Git, commands and arguments are inconsistent to some degree