Du bist nicht sicher, ob Git das Richtige ist?
Mit einer beliebten Alternative vergleichen
Weitere gute Alternativen zu Git
Bewertungen über Git
The only version control system you ever need to learn
Kommentare: 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.
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.
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.
The solution to team programming
Kommentare: My experience with GIT is better every day since it is a platform that I keep learning to use and the more I learn, the more I like it. I share code with my co-workers and when I work alone, it allows me to have my code updated and clean
Since I met GIT, life has become much easier for me at work. It is the perfect platform for teamwork, even if it is only for yourself because it helps you keep the code updated and ordered. With GIT you can version the work, having several alternatives of the same branch, add comments and keep the code clean. The platform compresses the code and helps you decrease time by uploading large amounts of changes very fast. There are tons of clients to handle GIT visually and many of them are free
The only thing I do not like is the documentation, when I have needed to consult information about some git command, I consult other web pages to clarify my doubts
Git out of here
Kommentare: 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.
It's very easy to create and initiate a copy of the repository
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.
No better version control
Kommentare: It disappears into the background of my workflows, and comes in clutch in a pinch - it hasn't failed me yet.
GitHub, the GitHub API in particular has been very useful in managing our codebases and automating deployments.
Merge conflicts, I don't know how fixing merge conflicts could be made more painless but if it is possible that would be awesome.
Everybody loves Git, including us
Kommentare: We don't know how we would exist without Git. Every organization needs source control and most developers are well-versed with Git without additional training. We continue to build on the experience to offer automated deployments that enforce better code quality across the board.
Git is the gold standard for source control. Its decentralized approach ensures that developers can easily test, break, and fix in local environments. It takes a merge-first attitude to ensure that all changes are understood and incorporated as new releases occur from multiple developers, increasing visibility to changes and overall code quality.
For those not well-versed with the command line, the GUI client versions don't serve the community well. They are often confusing and give less granular control than the command line.