Skip to content
Prev 18789 / 21312 Next

[Bioc-devel] Unable to Push Error

Hi Jim,

Thanks for looking at this. The GitHub repo I've referenced is even with my local master branch (when I push I get the message "Everything up-to-date" with working tree clean), and you can see that I merged the most recent version bump in the commit history here: https://github.com/max-mcgrath/discordant/commit/bb3b4761b241d7eb5002b5342dfec2068772eb84. I did bump the DESCRIPTION version number to 1.19.1 to trigger a rebuild when I push, but I did so after I merged the October 1.19.0 bump. I've also tried pushing from a fresh clone of the GitHub repo (after syncing with BIOC), all with the same results. When I pull from BIOC master, I receive the message "Already up to date", and then the push fails. I've searched my local repository thoroughly for long strings of "<", "=", and ">" using both visual inspection and terminal commands like "grep -r "<<<<<<<" * .[^.]?*" but have been unable to locate any merge conflicts. I apologize if I'm missing something obvious here, but as far as I can tell all remote commits have been merged locally (and on the GitHub remote), so I'm at a loss.

I'm not that experienced with python, but it appears that the pre-receive hook defined here https://github.com/Bioconductor/git-hooks/blob/master/prevent_merge_markers.py searches the git diff between the BIOC version and the new version for the string "<<<<<<< HEAD" (lines 93-96 and 67-77), and that string does appear in the git diff between the current BIOC version and my local copy (or a fresh clone of the GitHub repo) due to the deleted file containing the merge conflict. I've attempted a reproducible example below (for UNIX systems), but I'm pretty far out of my wheelhouse so I can provide any additional information if needed to resolve this issue.


git clone git at github.com:max-mcgrath/discordant.git

cd discordant

git diff -G "<<<<<<< HEAD" bb3b4761b241d7eb5002b5342dfec2068772eb84..1523b91eddb0bc46403438389a108e66efdb5c4e


Again, I apologize if I'm missing something obvious, but I've been trying to resolve this issue for some time and am at a dead end.


Thanks,

Max
Message-ID: <CY4PR05MB3381684B8BABA4521B3C8A7B84269@CY4PR05MB3381.namprd05.prod.outlook.com>
In-Reply-To: <MWHPR08MB3533C4A5361ECEE1C20F1E11C2269@MWHPR08MB3533.namprd08.prod.outlook.com>