Timeline for Cannot push to GitHub - keeps saying need merge
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 27, 2020 at 11:49 | comment | added | jeffery_the_wind | This is actually what I want to do but I just tried with Gitlab, and Gitlab doesn't allow this on "protected branches" by design | |
| Nov 20, 2019 at 1:23 | review | Suggested edits | |||
| Nov 20, 2019 at 7:32 | |||||
| Aug 1, 2018 at 11:15 | comment | added | moopet | This is a duplicate answer, and the original was not great advice anyway. | |
| Jul 20, 2018 at 9:43 | comment | added | Oliver Dixon | Great way to destroy a repository. If you force push you will destroy history. Also many professionally setup git code bases won't allow you to do this. | |
| Jun 30, 2018 at 14:34 | comment | added | Legends |
git push --set-upstream origin master --force
|
|
| Jun 14, 2018 at 11:17 | history | edited | Matthieu Moy | CC BY-SA 4.0 |
spell --force completely, so that people understand it's dangerous
|
| Jun 7, 2018 at 1:17 | comment | added | rollsch | It will work but it may not be what you want! It means you are basically just ignoring changes that will now be lost forever. | |
| Feb 12, 2018 at 6:19 | history | edited | Kailash Bhalaki | CC BY-SA 3.0 |
added 12 characters in body
|
| Feb 11, 2018 at 15:17 | review | Late answers | |||
| Feb 11, 2018 at 15:21 | |||||
| Feb 11, 2018 at 15:02 | review | First posts | |||
| Feb 11, 2018 at 15:10 | |||||
| Feb 11, 2018 at 14:57 | history | answered | Kailash Bhalaki | CC BY-SA 3.0 |