I believe most of the people who does not get along with Git, it is because they had a bad experience in first uses. The first impression is always a problem.
In Git, Command Line is your friend (believe it). In 90% of the time you always need the same commands for managing source code.
If you don't like to repeat steps, you can use aliases to group commands.
But when people start trying using features like rebase, cherry pick, things can get very messy. Don't go that way.
For managing visually your history, Git Platforms like Gitlab, Github, Bitbucket and others help a lot, including integration with issues, milestones, releases and package storage.
Edit: I did a QD plugin for opening the Git bash. It is way faster than clicking in three, four places.
Git can't be this terrible, what am I doing wrong?
in Source Code Control
Posted · Edited by felipe.foz
I believe most of the people who does not get along with Git, it is because they had a bad experience in first uses. The first impression is always a problem.
In Git, Command Line is your friend (believe it). In 90% of the time you always need the same commands for managing source code.
Edit your code
git add (file) git commit -m "Message" git push origin new_branch git checkout master git merge new_branch
If you don't like to repeat steps, you can use aliases to group commands.
But when people start trying using features like rebase, cherry pick, things can get very messy. Don't go that way.
For managing visually your history, Git Platforms like Gitlab, Github, Bitbucket and others help a lot, including integration with issues, milestones, releases and package storage.
Edit: I did a QD plugin for opening the Git bash. It is way faster than clicking in three, four places.