|
You are here |
arnorhs.dev | ||
| | | | |
vladimirzdrazil.com
|
|
| | | | | A collection of Git tips and tricks you might not know. | |
| | | | |
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 [...] | |
| | | | |
wittchen.io
|
|
| | | | | When you fork GitHub repository, you usually want to have your fork up to date with the original repository. You can update your fork in a few easy steps. Just look at the following example of the Git commands: Add the remote, call it upstream: git remote add upstream https://github.com/whoever/whatever.git Fetch all the branches of that remote into remote-tracking branches, such as upstream/master: git fetch upstream Make sure that you're on your master branch: | |
| | | | |
www.simpleprimate.com
|
|
| | | The other day I found myself having serious trouble publishing a new post to my blog. I was able to solve the problem through the use of Git rebase and I thought I would share my experience in case somebody else happens to go through the same thing. | ||