-
Notifications
You must be signed in to change notification settings - Fork 521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add more rebasing help #1536
Add more rebasing help #1536
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good! But it needs an extra explanation for when shit goes wrong like it did for me:
I merged an updated master into my branch and then got a merge commit. I ran git rebase -i origin/master
which actually started up a 1k commit rebase because my origin is my fork and its master is very outdated. I had to run git rebase -i upstream/master
instead because that's rust-lang/rust for me. I assume most people who struggle with git like this will probably have origin be rust-lang/rust but just to be sure we at least need a little help for those that dont.
ah good point, especially since the rest of the page assumes |
6ec11f3
to
2117a9c
Compare
Update books ## rust-lang/book 3 commits in a60f4316ec923a5ac2ed6a2eba6960edb832d855..2bd5d42c9956369132228da6409f0e68da56c51a 2022-12-22 21:37:10 UTC to 2022-12-22 21:36:14 UTC - fix macos installation problem (rust-lang/book#3469) - Update -guessing-game-tutorial incorrect output (rust-lang/book#3462) - FIX: IT repo updated (rust-lang/book#3454) ## rust-lang/nomicon 1 commits in dd37e21ccee43918ed18a71581bb2af537ffe4fc..8ca261268068d80c0969260fff15199bad87b587 2022-12-30 16:32:09 UTC to 2022-12-30 16:32:09 UTC - Discourage the use of transmute to construct invalid values (rust-lang/nomicon#388) ## rust-lang/rust-by-example 6 commits in 995df09b65c582eb6290ab7ea5d9485983eb4c37..8888f9428fe9a48f31de6bd2cef9b9bf80791edc 2023-01-01 12:53:50 UTC to 2022-12-21 10:18:31 UTC - types/alias: use io::{Result,Error} instead of Io{Result,Error} (rust-lang/rust-by-example#1660) - Fix sample code mismatching its comments (rust-lang/rust-by-example#1659) - fix: add missing space (rust-lang/rust-by-example#1658) - diverging: fix issues with example code (rust-lang/rust-by-example#1631) - Update enum.md (rust-lang/rust-by-example#1645) - Clean up Chapter 2 (Primitives) (rust-lang/rust-by-example#1651) ## rust-lang/rustc-dev-guide 5 commits in 8b42eb5..b3e2a6e 2023-01-01 05:20:47 UTC to 2022-12-25 12:11:21 UTC - Add help for when you update a submodule by accident (rust-lang/rustc-dev-guide#1537) - Simplify "how to build and run" section (rust-lang/rustc-dev-guide#1528) - Replace `$TARGET` with `host` (rust-lang/rustc-dev-guide#1514) - Add more rebasing help (rust-lang/rustc-dev-guide#1536) - Fix rustc_borrowck crate name typo (rust-lang/rustc-dev-guide#1535)
r? @Nilstrieb cc @camelid
The goal here is to add a section we can link to from the new tidy check in rust-lang/rust#105058 (comment). Originally I suggested linking to https://jyn.dev/2022/09/02/git-cheats.html#i-made-a-merge-commit-but-now-someone-is-telling-me-merge-commits-arent-allowed-how-do-i-fix-this-please-i-already-spent-3-hours-on-this-i-dont-want-to-spend-3-more and Nils suggested upstreaming it to the guide, but I don't think the section with
git reset
is actually very useful (if things are that broken, it's usually better to ask for help IMO) and I wasn't able to get my repo into a broken enough state to test it.