TrustRadius: an HG Insights company

Git Manufacturing Reviews & Insights

Score10 out of 10

73 Reviews and Ratings

Community insights

TrustRadius Insights for Git are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.

Business Problems Solved

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.

Git Reviews

4 Reviews
ManufacturingMechanical Or Industrial Engineering1Semiconductors1Computer Hardware1Aviation & Aerospace1

Git: Branches are cheap, damn cheap

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

It's widely used by our component owners to store all the libraries. The beauty about Git compared to others is that it stores snapshots instead of deltas, which makes it just much much faster and more reliable to store code within it. We have integrated Git with Gerrit which stores the whole organization's Git repos within it, thus making it more reliable and scalable.

Pros

  • Fast.
  • Robust.

Cons

  • This tool is just perfect.

Likelihood to Recommend

It is well suited for scenarios wherein you need to manage a lot of code and multiple developers are working on the same repository. The whole point of using Git is that you can create branches, develop the code on it, push it up and again keep on doing this. If you are not creating 10 branches a day you are not using GIT well.

Alternatives

Perforce
What I know is Perforce and CVS, such other repos tend to store deltas while Git stores the snapshots of the stuff as their commit ID's. This is what makes Git much much faster when you are developing on huge repos, since the checkouts are just instantaneous.
Vetted Review
Git
3 years of experience

The version control system you need!

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

Git is one of the source code version control tools used at my organization. We are using Git (Gitlab) to store our source code across multiple repositories. We have a mainline development branch which all our new code is eventually pushed to after being code reviewed by their branch using pull requests.

Pros

  • Ability to create branches and merge those changes in.
  • Diff-ing changes.

Cons

  • Many different GUIs, many people.
  • Understanding Git has a little bit more of a learning curve when compared to other source control solutions.

Likelihood to Recommend

Developers can work parallel on projects, increasing the speed at which teams can work, thus causing projects to complete faster. Git has saved our organization hours of having to manually trace code to a breaking change or manage conflicting changes.

Alternatives

Mercurial and Apache Subversion
After using Subversion previously for years, Git comes across as the new and improved source control approach.

Git things done

Rating: 9 out of 10
Incentivized

Use Cases and Deployment Scope

In our organization, Git is used by several departments for file versioning, collaborative work on the same source code, change tracking, branch merging, version comparison etc. Especially because we have distributed teams all over the world, we needed a reliable tool to achieve these goals, and Git was the natural choice.

Pros

  • 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.

Cons

  • 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.

Likelihood to Recommend

Git is suited for doing source code versioning of all-size projects, from small to large and very large. Does very well when you have distributed teams, as it increases the team's focus, collaboration, decreases the time needed for merging code and finding differences between file versions, and decreases the time needed to make a software release. Therefore, the time to market of new projects or new features is improved (any top manager's desire).

Alternatives

Apache Subversion
Compared to SVN, Git has a decentralized approach which increases collaboration in the team by enabling the local stored branches. There is no need to be connected to the repository(via an internet link) to work and commit code. Besides the fact that the performance of Git is superior compared to SVN, it also has better support for merging and branches. A plus for SVN would be that it is easier to learn.

An excellent tool to keep all the changes updated

Rating: 10 out of 10
Incentivized

Use Cases and Deployment Scope

Git is only used in our department. All our code is saved and versioned with Atlassian Stash using Git as version control system. There are at least 15+ projects in the development using this VCS.

Pros

  • 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.

Cons

  • 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.

Likelihood to Recommend

I think you can use Git for every project you have, there aren't limitations about a kind of program or something specific. It's more about personal preferences and ease of use.

Alternatives

Apache Subversion
Git is a distributed version control system. There is more flexibility to work with a bigger team. You can modify the same file and later merge all changes into a single file.