Timeline for Squash all my commits into one for GitHub pull request
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 19 at 18:51 | comment | added | Tobias | Usually not a good idea to force push to master. You'd want to squash your commits on your feature branch instead. | |
| Mar 24, 2021 at 19:49 | comment | added | banderlog013 |
it is better to use --force-with-lease
|
|
| Sep 17, 2020 at 16:56 | comment | added | Barlas Apaydin | I got conflict. Thank you very much for this. No one mentions about this in no other answer. | |
| Dec 26, 2015 at 20:45 | comment | added | Léo Lam | @luckykrrish That's a perfectly acceptable thing to do on your own PR branch. | |
| Dec 3, 2015 at 12:58 | comment | added | Justin Skiles | @luckykrrish How does one squash commits on a public pull request then? | |
| Mar 19, 2015 at 17:10 | comment | added | sebnukem | what does "up to" mean exactly? Is xxxxxxxxxxx included or not included? | |
| Nov 29, 2014 at 9:49 | history | edited | omerjerk | CC BY-SA 3.0 |
deleted 4 characters in body
|
| Oct 16, 2014 at 10:45 | comment | added | luckykrrish | It's not a good idea to force push or rebase a branch that is already pushed to remote. All other people who had the un-rebased master branch will get an error, and they will be confused. | |
| May 14, 2014 at 3:24 | vote | accept | omerjerk | ||
| May 14, 2014 at 3:25 | |||||
| Jan 26, 2013 at 8:25 | history | answered | omerjerk | CC BY-SA 3.0 |