You are here |
www.erikschierboom.com | ||
| | | |
blog.danskingdom.com
|
|
| | | | Git is super powerful, but can also be confusing, especially when using the command line interface (CLI). It has so many commands, and I only regularly use a handful of them. | |
| | | |
cmetcalfe.ca
|
|
| | | | Git checkout - autocomplete local branches only | Having Git autocomplete branch names when doing a checkout is super useful. Having the autocomplete... | |
| | | |
www.aaron-gray.com
|
|
| | | | You can run rubocop on just a local branches' changes like this: git fetch && git diff-tree -r --no-commit-id --name-only master@{u} head | xargs ls -1 2>/dev/null | xargs rubocop --force-exclusion Then you can create 2 corresponding aliases in your terminal .rc file to make this easy to remember: # Alias to run rubocop on the current branch's diff from [...] | |
| | | |
jiby.tech
|
|
| | Every now and then, at work, I find myself discussing git worfklows, commit messages, branching, releasing, versioning, changelogs etc. Since my opinion has remained fairly consistent for the past few years, I found myself repeating the same points a lot, so I wrote it down. This page is the resulting compilation of my opinions on the software development lifecycle (SDLC), without workplace-specific tangeants. The article is broken down into ideas + recommendations, with recommendations in bold. |