I only do that if the "bugfix" is miniscule; I've forgotten stashes, and had severely painful efforts to merge them back in. Now I only stash for a very brief period of time.
Otherwise, I use a new topic branch instead of stashing. Branching takes so little effort.
Had branches on the mind and didn't catch it till just now and the edit window is closed.
For the most part you can tweak most of the configs via command-line: git branch, git remote, or git config. I switch between those and editing the .git/config directly depending on the scope of the changes.
Comments
That was worth reading to find out that I could rename origin to github. For some reason I find the word origin really confusing.
There's a couple of other good tidbits in there if you're still a git neophyte like myself.
For example, this bit:
# git stash (all my changes are saved away, and I have a clean tree)
# Fix the bug
# git commit -a -m "bugfix"
# git stash pop (changes are back)
This is the type of stuff that make SVN people "get it".
I only do that if the "bugfix" is miniscule; I've forgotten stashes, and had severely painful efforts to merge them back in. Now I only stash for a very brief period of time.
Otherwise, I use a new topic branch instead of stashing. Branching takes so little effort.
I've lost code with stash. Be wary.
I didn't catch how, could you explain?
Rename 'origin' to 'github' in .git/config. This is from the 'ENLIGHTENMENT' section in the article.
Or just run the command
git branch -m origin github
Ooops... my bad should have been
git remote rename origin github
Had branches on the mind and didn't catch it till just now and the edit window is closed.
For the most part you can tweak most of the configs via command-line: git branch, git remote, or git config. I switch between those and editing the .git/config directly depending on the scope of the changes.