Timeline for Cannot push to GitHub - keeps saying need merge
Current License: CC BY-SA 4.0
52 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 7, 2023 at 9:30 | answer | added | jsHate | timeline score: 0 | |
| Dec 28, 2022 at 23:49 | history | edited | starball | CC BY-SA 4.0 |
no need to say you're new to X: https://meta.stackoverflow.com/q/296391/11107541
|
| Aug 3, 2020 at 20:23 | answer | added | abhinav kumar | timeline score: 0 | |
| Jul 29, 2019 at 16:31 | history | protected | Anshul Goyal | ||
| Mar 15, 2019 at 20:44 | answer | added | Aman Mishra | timeline score: 2 | |
| Aug 29, 2018 at 4:48 | answer | added | primegxy | timeline score: 63 | |
| Jun 14, 2018 at 11:02 | answer | added | Ivan | timeline score: 3 | |
| Feb 25, 2018 at 11:57 | answer | added | Suman Astani | timeline score: 2 | |
| Feb 11, 2018 at 14:57 | answer | added | Kailash Bhalaki | timeline score: 19 | |
| Jan 28, 2018 at 10:05 | answer | added | Mahi | timeline score: 0 | |
| Nov 24, 2017 at 7:16 | answer | added | Pyuri Sahu | timeline score: 34 | |
| Oct 16, 2017 at 8:44 | comment | added | Dan M. CISSOKHO | In my case I forgot to use the branch name : git push -u origin branch_name | |
| Oct 11, 2017 at 23:29 | answer | added | Vikash Raja Samuel Selvin | timeline score: 0 | |
| Aug 28, 2017 at 9:41 | answer | added | ScottyBlades | timeline score: 7 | |
| Aug 22, 2017 at 12:15 | answer | added | VIKAS KOHLI | timeline score: 7 | |
| Mar 16, 2017 at 15:30 | answer | added | XMAN | timeline score: 0 | |
| Jan 20, 2017 at 21:04 | comment | added | mariotti | I got the same problem, and not solved by the simple git pull -- all. It is indeed a new repo, clean, but with license added, a service added to show progress on README.md. Before these addition it worked nicely from the cmd line. Which one is the tip? | |
| Jan 20, 2017 at 9:17 | answer | added | Bhavuk Mathur | timeline score: 20 | |
| Nov 15, 2016 at 6:31 | answer | added | Sai prateek | timeline score: 4 | |
| Sep 2, 2016 at 9:53 | answer | added | Component 10 | timeline score: 5 | |
| Aug 19, 2016 at 21:27 | answer | added | watashiSHUN | timeline score: 4 | |
| Jul 14, 2016 at 13:05 | comment | added | vikramvi | This error also comes post squash and trying to push to remote | |
| Jul 6, 2016 at 10:24 | history | edited | Anthony Geoghegan |
not specific to GitHub
|
|
| Mar 3, 2016 at 14:29 | review | Suggested edits | |||
| Mar 3, 2016 at 15:39 | |||||
| Nov 1, 2015 at 10:34 | history | edited | Peter Mortensen | CC BY-SA 3.0 |
Copy edited (e.g. ref. <http://en.wikipedia.org/wiki/GitHub>).
|
| Jul 22, 2015 at 13:58 | answer | added | Marco | timeline score: 6 | |
| May 27, 2015 at 14:32 | answer | added | 9swampy | timeline score: 3 | |
| Apr 21, 2015 at 10:04 | answer | added | Ramon Fincken | timeline score: 5 | |
| Mar 5, 2015 at 16:26 | comment | added | developer747 | Its trendy to praise git. But almost every developer I talked to, privately agree that they personally hate git. Now that they use git they spend so much more time in source control compared to what they used to spend when they used perforce or TFS. | |
| Jan 13, 2015 at 9:42 | comment | added | rh979 | @RuslanKabalin - but GitHub itself recommends to add ReadMe and if someone unchecks it, it prompts you to add it manually :) | |
| Sep 7, 2014 at 7:13 | answer | added | wisbucky | timeline score: 4 | |
| Jul 29, 2014 at 16:17 | answer | added | Teo | timeline score: 50 | |
| Jun 3, 2014 at 18:09 | answer | added | prayagupadhyay | timeline score: 127 | |
| Jan 25, 2014 at 6:02 | answer | added | Thomas07vt | timeline score: 14 | |
| Jan 14, 2014 at 10:47 | comment | added | Deleplace | @Echelon the -f option to force the push is dangerous. I just used it in a team project and 6 commits were "striped", simply deleted from server and no way to get them back! | |
| Nov 23, 2013 at 5:05 | answer | added | fox323 | timeline score: 4 | |
| Oct 14, 2013 at 14:30 | comment | added | Ruslan Kabalin | Seen a complain about this from git newcomer. The reason is that when they create a new project on GitHub, they leave tickbox "Initialise with readme" or choose .gitignore/GPL options, so new project already has a commit they do not have locally, thus the confusion caused by error above. | |
| Sep 9, 2013 at 16:16 | history | edited | Nick Rolando | CC BY-SA 3.0 |
edited title
|
| Aug 8, 2013 at 20:08 | answer | added | Nick Rolando | timeline score: 783 | |
| Jul 18, 2013 at 17:49 | comment | added | viki.omega9 | @Echelon I wonder why it dreams so much. This has happened to me a couple of times. (and each time I forget how to fix it :P) | |
| Jun 24, 2013 at 15:27 | comment | added | Sumit Kapadia | you can refer stackoverflow.com/questions/12650261/… | |
| May 28, 2013 at 14:37 | comment | added | Echelon | @ThorbjørnRavnAndersen - I managed to fix this scenario using 'git push -f' which seemed to make git forget about its imaginary problems :) | |
| Apr 10, 2013 at 1:33 | answer | added | longda | timeline score: 5 | |
| Feb 19, 2013 at 9:27 | comment | added | Thorbjørn Ravn Andersen | Note that this can also happen for branches previously visited locally, which have had commits in the upstream repository. Is there an easy way to just fast forward such an old branch or simply let git forget about it in the local repository? | |
| Nov 19, 2012 at 6:14 | answer | added | xiatica | timeline score: 35 | |
| Jul 19, 2012 at 21:18 | answer | added | Hemant | timeline score: 3 | |
| Apr 25, 2012 at 12:48 | history | edited | mtvec | CC BY-SA 3.0 |
added 2 characters in body
|
| S Apr 24, 2012 at 14:09 | history | suggested | AYK |
Added tag git
|
|
| Apr 24, 2012 at 13:02 | review | Suggested edits | |||
| S Apr 24, 2012 at 14:09 | |||||
| Apr 24, 2012 at 13:01 | answer | added | Jake Greene | timeline score: 247 | |
| Apr 24, 2012 at 13:01 | answer | added | AYK | timeline score: 202 | |
| Apr 24, 2012 at 12:56 | history | asked | user1353717 | CC BY-SA 3.0 |