DOC: Rebase/squash instructions confusing
See original GitHub issuehttp://docs.astropy.org/en/latest/development/workflow/development_workflow.html
What I propose…
How to rebase
git fetch astropy master
git rebase astropy/master
(We should be consistent about naming the “upstream” remote, and it seems like astropy
is the one to use from Double check your setup.)
How to squash
git rebase -i HEAD~n
where n
is the number of commits to consider. For example, to squash last three commits into one, you would do git rebase -i HEAD~3
, “pick” the first one on top, and “squash” the second and the third in the subsequent step involving an editor you set up to use with git
.
cc @mcara
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (11 by maintainers)
Top Results From Across the Web
git-rebase Documentation - Git
By default, a rebase will simply drop merge commits from the todo list, and put the rebased commits into a single, linear branch....
Read more >Using Git rebase on the command line - GitHub Docs
Here's a short tutorial on using git rebase on the command line. ... We'll start our rebase by entering git rebase --interactive HEAD~7...
Read more >029 Interactive Rebase Options - YouTube
Here I cover every option of interactive rebase : pick, reword, fixup, squash, edit, and exec.If you haven't seen my previous videos on...
Read more >Merging vs. Rebasing | Atlassian Git Tutorial
Compare git rebase with the related git merge command and identify all of the potential opportunities to incorporate rebasing into the typical Git...
Read more >Rebasing Step-by-Step - Git for Teams
A ch10.asciidoc Falling back to patching base and 3-way merge. ... So I've still got the file (great!), but Git is also confused...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I would argue that it would be very much useful to spell out somehow that
git pull
is a command that should never be used during the rebase procedure. I finally got the exact recipe of how the usual rebase mistakes are created. Not sure where that idea comes from for that very common mistake (certainly not from these dev docs), but I suppose it wouldn’t hurt to emphasize that it’s not a command that needs to be done.Hmm… 🤔