Skip to content
Snippets Groups Projects
Commit 5cec7230 authored by bbartels's avatar bbartels
Browse files

Update how_to_use_git.md

parent fc9c2192
No related branches found
No related tags found
No related merge requests found
...@@ -96,6 +96,23 @@ git push origin master ...@@ -96,6 +96,23 @@ git push origin master
If all succeeds, you should be able to see your commit on Gitlab. If all succeeds, you should be able to see your commit on Gitlab.
#### WTF? I have to remember all of that?
That was the exhaustive list to cover all of the worst case scenarios. Typically
things go much smoother:
```
git pull origin master # get most recent stuff from Gitlab
# make some changes
git add . # stage files to be committed
git commit -m "change something" # commit the staged files
# make some more changes
git add . # stage files to be committed
git commit -m "change something else" # commit the staged files
git pull origin master # pre-emptively merge Gitlab's master into mine
git push origin master # sync my 2 commits to Gitlab's master
```
It really isn't that bad once you use it for a week. Just don't panic when you
get your first merge conflicts 😉
## Other workflows ## Other workflows
What we just described is the bare minimum Git workflow. Most people don't like What we just described is the bare minimum Git workflow. Most people don't like
working this way. We encourage you to research other workflows, like a Git working this way. We encourage you to research other workflows, like a Git
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment