Timeline for answer to How do I squash my last N commits together? by aabiro
Current License: CC BY-SA 4.0
Post Revisions
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 16, 2024 at 4:29 | comment | added | Vitaly Zdanevich |
git rebase -i HEAD~2 but for some reason I see the full git history - any idea why?
|
|
| Sep 16, 2021 at 22:50 | history | edited | aabiro | CC BY-SA 4.0 |
added 17 characters in body
|
| May 15, 2019 at 14:40 | history | edited | aabiro | CC BY-SA 4.0 |
added 124 characters in body
|
| Dec 31, 2018 at 13:36 | history | edited | aabiro | CC BY-SA 4.0 |
added 2 characters in body
|
| Nov 30, 2018 at 16:51 | comment | added | aabiro |
The rebase will happen in blocks as it goes through the commits on your branch, after you git add the correct configuration in your files you use git rebase --continue to move to the next commit and start to merge. :x is one command that will save the changes of the file when using vim see this
|
|
| Nov 30, 2018 at 12:20 | comment | added | not2qubit |
Please also explain what the --continue and vim :x does.
|
|
| Sep 11, 2018 at 13:47 | history | edited | aabiro | CC BY-SA 4.0 |
added 25 characters in body
|
| Jul 11, 2018 at 9:35 | history | edited | aabiro | CC BY-SA 4.0 |
added 24 characters in body
|
| Jul 10, 2018 at 22:51 | review | Late answers | |||
| Jul 10, 2018 at 22:54 | |||||
| Jul 10, 2018 at 22:28 | history | answered | aabiro | CC BY-SA 4.0 |
