Git Reviews

The only version control system you ever need to learn

Comments: I've used many version systems over the years and Git by far is the most sane and useful. It's the de-facto VCS for a reason. There will be an initial learning curve, but even if you don't want to use Git directly, there are so many tools and UI's that build on top of it to help guide you through it and automate away some of the tedium.

Pros:

It's free, it's easy to get started with, and it's powerful. There is a strong ecosystem of tools and platforms built on top of Git, so you can do new and powerful things. And it makes it extremely easy to collaborate with colleagues, even when you're working on the same file.

Cons:

There is a bit of a learning curve, particularly around some of the more complicated workflows like rebasing or performing 3-way merges, but once you've learned it, you're set for life.

No software can be done without Git

Comments: I have never had any big issues with git so far, I recommend this tool to all devs

Pros:

It is so easy to learn an implement, also there are a lot of cloud repositories that support it

Cons:

With large amounts of code, it starts to be slow.

Git out of here

Comments: It's easy to get it to do what you want if you know all the switches and the options, you won't get warnings if something fails, you have to switch from web to IDE to CLI so each helps you progress in the task. Good for open source while you're not the one managing the code.

Pros:

It's very easy to create and initiate a copy of the repository

Cons:

It's distributed so no backup is done to your work is done till you push it to the repository, no one organization to give you support, doesn't handle empty folders (no warnings is given), no easy move files with history from one repository to another (while keeping history in the source repository), no one view to control your actions - need to move from your IDE to web to CLI, each sub module is presented by SHA number and not tag and version, if you have sub modules and you do git clone URI then you would get empty folder (no warning again) because that's the default. History is stored locally and consumes disk space (instead of at least connecting to the remote server as an option). Other than CLI there's no official supported GUI. There's much more like the need to have gitlfs client.

Git - review

Pros:

Git is an essential part of my project and development process. It allows me and my team to control versions of the code and collaborate effectively. Lots of commands, work seamlessly across different tools.

Cons:

I didn't find any issues with Git. To me it works perfectly fine.

GIT for the PHP Develop

Comments: the experience is good in over all, but if design a GUI to manage the source code, the system can be perfect.

Pros:

Is useful, simple, light and have many commands that help to manage the changes in the source code

Cons:

Not have GUI that help to manage branches, clone repos and merge the change to the master, and reverse changes.

Essential source control tool

Comments: It's very important to maintain good source control. Git makes this extremely easy and even allows you to return to a previous version of your code, for example. Very valuable control.

Pros:

It, especially in combination with tools such as GitHub, makes for a very powerful code tracking and collaboration system.

Cons:

The different terms and commands are not too easy to understand as a beginner.

A great experience to manage repositories

Comments: A great experience to manage repositories

Pros:

Its easy integration with IDE tools is a key part of this tool

Cons:

Problematic to rebuild branches when something corrupts it

Git: A fantasstic tool

Pros:

I love Git because it helps the communication between Github and your local machine directly on terminal.

Cons:

It could be counter intuitive for people not very familiar with terminals.

A great experience to pull/push code from repository

Comments: A great experience to pull/push code from repository

Pros:

Awesome tool to work as a team on repositories with VCS

Cons:

Sometimes it becomes difficult to use it through command prompt.

A great tool to gather repository code from many VCS tools.

Comments: A great tool to gather repository code from many VCS tools.

Pros:

its easy way to get repository data by simple command line executions

Cons:

nothing specific I dislike from GIT, it has met all my needs

Have better experiences with git

Comments: I admit my experience with this tool called git is very good. I am improving with this tool daily. It helps me solve a lot of problems. All my relatives use it I assure you.

Pros:

When I use this tool called git, it never fails. It does the job you expect from this tool perfectly. Git helps me enormously in my various that I carry out daily.

Cons:

Git for a beginner is very difficult to find. Those who have created this tool must put other means, use other techniques so that the beginner who is interested in the tool can use it easily.

GIT - Source Code Management

Pros:

I like the ease use of git in the cli and fhe integration with the many tools

Cons:

I do no have anything, i can comply git.

One of the Most Popular Version Control Software

Pros:

Git is one of the most popular and powerful version control software. It not only tracks your changes, but it also capable of cooperation with other teammates.Another highlight is everyone can create their own "branch" then merge to the master repository after they've finished their own works. This reduced codes clash and keep the master repository tidy.

Cons:

Git is very easy to get on but requires extensive time and energy to mastering it.

A Must

Comments: I cannot imagine my day as an engineer or a developer without a version control technology as Git, specially working in CI/CD.

Pros:

Easier collaboration, as we as developers work together and put our work together.

Cons:

It is only a command-line interface, but with other tools it will be superior.

Git Review

Comments: This software makes programming projects easy to work on. I am able to collabrate with other developers on the same project and this does not affect the code because it's branching capabilities prevents code interference and ensures proper code mamangement.

Pros:

The version control feature has been really helpful to me as a junior developer, as it helps me track versions of my code and also collabrate with different developers.

Cons:

Could be a bit confusing for a new user, you might need alot of help from the onset but becomes easy to use as you consistently use it.

I normally use git every day without any problems or issues. Thanks to git they are best.

Pros:

The entire version of Git is so easy to use and it does every task and operation perfectly well. And it is the best tool for software developers.

Cons:

The issue is the UI, apart from that Git is absolutely working perfectly and they are the best.

Very powerful version control system open to your own work style

Pros:

Git is a decentralized version control system. Decentralized means that the system does not force any node to be a ‘server’, ‘main’ or ‘master’ node, and that every node has a full copy of all the information. This feature makes Git a very powerful tool, as it lets you build the workflow that is best for you (wether its a simple server/client model or a more complex workflow with a server, developers and a code reviewer/integrator). It also means that if there is a failure in a node (eg the repository is deleted), any other node (or copy of the node) will do as a server with no change. It is open source and free, and it is used in very large projects (it was created originally to manage the Linux kernel code). It means good community support and that it has been tested in critical production environments.

Cons:

Git is a command line tool. It has not any visual feedback (more than white text over black background) and all the commands must be typed. It is powerful but it also means that it has a lot of commands to remember and some learning curve. But probably the first thing you will do after installing Git will be to install a graphical tool that can ease its use. If you are setting up a ‘central’ node, you have the same scenario: set it up manually by yourself or find some service already compatible with Git (github.com, AWS CodeCommit, Atlassian Sourcetree…). Also, there is no a ‘right’ way to use git. You will have to find the right workflow for your project or team. Play with it, try some workflows (google ‘git-flow’ for starters), choose the one that is best for you, and make sure that everybody in your team understands the chosen workflow.

I had to learn how to use it, but after that, git has become an integral part of my daily workflow

Comments: I am a huge fan of git, so much so I teach it to freshmen level students whenever I get a chance. I clearly remember two times where my hardware has crashed beyond repair, but since I use git and remote repositories, I have not lost any work even in these situations. What a lifesaver! Beyond that, I use multiple computers (I have an iMac, Ubuntu laptop, some Windows desktops) and git works great on each machine. I can start working on some feature on one machine, push my changes, and the pull and continue work on a different machine. If I make mistakes I can go back to a previous commit. The freedom and level of security I have in not losing my work are the two biggest reasons why I like git so much. Overcoming the initial learning curve will be worth it.

Pros:

* Git is cross platform; you can use it on windows, linux and mac and it works the same way on each operating system (I have personally tried each) * Installing git on each platform is a breeze * All IDE's I use integrate with git (e.g. Jetbrains IDEs, VS Code, VS) * You can use git through terminal, IDE interface, or a separate git GUI app like Sourcetree * It is very rare to find software that offers this much flexibility, and at the same time, so much consistency across each operating system! * Some of the biggest OSS platforms use git - by learning how to use git, you can share your code with the rest of the world

Cons:

Git requires you learn the different commands and terminology. 7 years ago, when I first started using git, I remember it took me several days to get comfortable using the commands. Luckily the set of commands for basic usage (clone, commit, pull, push, branch and merge) is not overwhelming. After mastering these basic commands, git is easy to use and extremely practical.

Version controlling is Essential for software companies of any size, it helps in many ways

Comments: Git is a really great software for version controlling and code base management, i have a really great experience with it, deployment and development cycle has become simpler with the help of git

Pros:

Git is a majorly used tool which is used by big companies to the individuals who are involved in software development or coding, the benefits of Git is that you will not be lost in changes, you have the history of the files edited , at any time you can revert back to the old changes, version control is important for lose recovery etc ... 2 or more can work on parallel on a same file and merge it later one by one, helps resolve merge conflicts, this improves the productivity in the team , at the time of unstably we can always revert back to the stable version, you can review the code of other developer, there is a concept called pull request to merge the changes to the parent branch, at the time of this the code review can be done , which is one of the best practises n the product developmental lifecycle migration from one git service to another is very simple, you need not delete and reclone, there is a command to change the server URL thats it, it has a large set of git commands using which you can do many good operations, one of which is cherry pick , using cherry-pick we can fetch only a required pice of commit into another branch, you can reset head and create a branch out of there to create a branch out of a older version etc , its all normal we can do everything in git that we do with a normally maintained version manually (assume if you are storing all versions in the folders), space effective storage of each versions,it is stored them logically

Cons:

Git is absolutely perfect in my eyes, one thing is they have a good CLI but for new non terminal users they could develop a UI interface, any how other softwares serves this purpose,

Tool to handle Version controlling, parallel development and merge and recovery of code changes

Comments: Git is a must use tool for a productive and high quality software development, I had a really great experience using GIT

Pros:

The Git is a very useful and must be used tool for developing software, Some of its important features are, Version controlling - any changes that you commit to your repository will be maintained, you have the flexibility to switch between the changes , all the historic changes are maintained Branching - You can create a branch out of a parent branch and make your development in the new branch and merge it back to the parent branch this help's in parallel development , not spoiling the parent branch, code review can be connected before merging, Diff checking, we can check the difference between commits and branch to identify the changes and to understand the changes, Gives confidence to the developer, since all the changes are accessible, even if we mess-up the code there is a fallback available, Git can be used for CI/CD pipelines and deployment automation using tools such as Jenkins, it has a amazing command-line interface and good community support

Cons:

There are no possible issues with GIT, The only use case that is little difficult is, the Merge conflicts, Git dose a very good job of showing us the conflicts, but some times it is little mixed up , so could put a little bit work in mitigating it Git has a amazing CLI but would like to have some SDK and Console interfaces too, the point is the complex operation that could be done with CLI cant be achieved by any other interfaces

The best version control system!

Comments: Being a daily coder, git is one of the best VCS I've ever used. The interface is so intuitive and user-friendly, I quickly got on board with it. I also love how in-depth the tutorials are, it really helped me and my team become efficient with Git in no time. Definitely recommend this to anyone who needs a solid, powerful and user-friendly source code management solution.

Pros:

Git came with a sleek interface, and it syncs up with all of the other git clients. It is cross platform, which means it works well on Windows, MacOS, and Linux which is one of my favorite things about it. It took me a few hours to figure out some of the features, but once I did, I was able to use them without any issues.

Cons:

Git is the best software that I have ever used. It has been so easy for me to stay on top of my projects and tasks because of how effectively git organizes everything. I have never had a problem with git.

Awesome Version Control Management

Comments: While there is a slight learning curve involved with using Git, once you get the workflow down you'll wonder how you ever programmed without it.

Pros:

Git is a version control manager for software projects that allows code versions to be handled through a command line interface. For a project, a master version contains the core project. Branches can be created from a master to develop without affecting the master branch and to add new features to a project. Local and remote repositories are also managed. Git is also compatible with online services, such as Github and Atlassian Bitbucket to sync up offline repositories with the service. Documentation for the system is excellent, with great official documentation as well as plentiful user support and documentation available. Git is very robust and comes ready for use in large-scale, production programs.

Cons:

For less experienced users or people using Git for the first time, it might be temping to use GUI tools or services, but in order to learn Git properly it's best to use it by itself and through the command line. There are a lot of commands in Git that may seem daunting at first, but chances are you'll only be using a few of them in most cases and you should be able to Google rarer use cases.

Essential tool for every coding project

Comments: Git is a wonderful version control tool which has been essential to every professional coding project I've worked in. It may have a steep learning curve when going beyond simple pushes and pulls, but today I can't imagine working without git.

Pros:

- Lots of features for people working together on the same codebase, from simply making and reading changes on a repository, to more complex features for resolving conflicts and finding when/ how a bug was introduced. - Many code editors integrate easily with git projects. - Well documented and easy to find tutorials on the internet.

Cons:

It may not be so easy to learn how to properly use its more advanced features, as command line is not exactly obvious. Some graphical interfaces help with performing some simpler git commands, but they tend to hide how things work underneath so they don't help much with learning how to do things yourself.

Review for Git

Comments: Many popular web based repository hosting services are wrapped around git. Hence, in one way or another we work with Git everyday. I believe it is the best version control system I've worked with thus far.

Pros:

Git is free and extremely easy to use. Even thought it has many different GUI clients such as Sourcetree, TortoiseGit,Fork, SublimeMerge etc etc, the command-line it self is extreme fun to use once you get the hands of the commands. There are zillion documentation and help all over the internet for any beginner to learn.

Cons:

One might struggle a bit when first learning and using command line in git. Merging could be a disaster if you don't get it right. However, later you will realize it is the easiest way to steer a version control system and will start loving it.

One version control to rule them all

Comments: Before git the code was often managed by a central gatekeeper and was reviewed and modified much less. Git allows you to break and test code without worrying that you will lose progress. It is essential to modern development!

Pros:

Its distributed, so there is no single point of failure. Logically, the branching model makes sense. It allows for very flexible collaboration with others. There is a record of changes, making it easy to lay blame when something is broken. New users can learn around 6 commands and immediately be productive.

Cons:

Out of the box there is no security. There is also no obvious wasy to secure certain branches (like master) from other teammates. You either have access to the origin repository or you don't. If a disk is full when push to remotes it will leave those remotes in a broken state.