Gitcards (@gitcards) header
Gitcards (@gitcards) profile picture

level up your git knowledge

England, United Kingdom
Joined April 2018
Photo by Gitcards (@gitcards)Photo by Gitcards (@gitcards)Photo by Gitcards (@gitcards)Photo by Gitcards (@gitcards)Photo by Gitcards (@gitcards)Photo by Gitcards (@gitcards)Photo by Gitcards (@gitcards)Photo by Gitcards (@gitcards)Photo by Gitcards (@gitcards)
Holy shit, is @elixirlang about to get super fast? github.com/erlang/otp/pull/2…
3
21
2
63
The prize is waiting for it's winner! If you are at @ElixirConf don't forget to try our quiz! And feedback is always welcome here!
3
9
Highlights from Git 2.24 buff.ly/2NdVzRU #git
1
1
I fucked up Git so bad it turned into Guitar Hero
215
10,627
223
14,579
Replying to @bitfield
You should add [help] autocorrect = 1 to your .git/config file. Or run the command git config --global help.autocorrect 1 to set it up globally. It'll automatically correct simple typos like this! nathanhoad.net/git-autocorre… From Git docs: git-scm.com/book/en/v2/Custo… #git #protip
2
18
4
45
I spy a highly requested black mug 👀
12
22
3
204
Ever annoyed by the long list of local Git branches that are no longer relevant? Solution: git remote prune origin That removes all local branches that have been deleted from remote (typically GitHub) Add --dry-run to merely see a list first to confirm. #git
20
429
32
2,008
- Fix last commit message - Change branch name - Added a wrong file in the repo - Everything went wrong { author: @i_AnkurBiswas } dev.to/teamxenox/git-hacks-y…
43
1
149
git debugging flowchart
37
1,015
6
1,187
#Git is a powerful tool, but it can be tricky. Here's a step-by-step on how to merge. "A Tutorial on Git Merge" - DZone Web Dev buff.ly/2KtusPF
1
4
15