Wednesday, March 14, 2018

git rebase --skip

This should be used if you are in step 3 of 4 of a rebase and you cannot commit because it appears you are caught up. This command, at a Git Bash shell, should let you go on to the next rebase. I realized just today that the Atlassian Bitbucket magic for aggregating commits does not exist in the Git Bash space and the longer an outstanding pull request lingers unmerged the more rebasing you will have to do against it to accommodate all of the other pull requests that were merged before yours. Once again, I am in an environment where the tooling gets in the way of checking in early and often. It's infuriating. It's seeming really stupid and backwards now that I know the grass is greener on the other side of the fence too. I know the answer to the "Do you see yourself as having any weaknesses?" interview question.

No comments:

Post a Comment