All of the sudden, we are seeing Releases / Tags showing up in one of our GitHub Repositories from another GitHub Repository (which consequently is also showing our releases). This is quite weird and neither repo owner has a clue as to how this may have happened. Does anyone know how to fix this? Thanks!
Asked
Active
Viewed 60 times
1 Answers
1
Creating a release in GitHub means pushing a tag, and adding a release title.
So you might have pushed tags named similarly between your two repos.
The OP David Poindexter confirms in the comments:
It appears [a colleague] accidently pushed 14 commits to the wrong repo/branch (nvisionative/nvQuickSite/master).
You can:
- delete the releases
- export commits through cherry-pick (or through format-patch for two completely separate repos)
- reset your branch (with
reset --hard+push --force, provided you communicate that reset to other collaborators)
VonC
- 1,042,979
- 435
- 3,649
- 4,283
-
How are tags related to completely different repos? They're not even a fork of each other. The code base, solution, and everything else is all different. The only thing that is the same is that the contributors happen to be in both repos. – Will Strohl Jan 23 '18 at 18:04
-
@WillStrohl Not sure: maybe a script which selected the wrong repo when creating the release? – VonC Jan 23 '18 at 21:07
-
I agree with @WillStrohl (owner of the other repo). These repos are nothing alike. The only similarity is that we are both contributors. I have confirmed, when I edit my releases (nvQuickSite), directly on GitHub, I see the proper tag associated with each release. Will can you check yours to confirm? – David Poindexter Jan 24 '18 at 15:25
-
I figured it out. It appears @WillStrohl accidently pushed 14 commits to the wrong repo/branch (nvisionative/nvQuickSite/master). Should I just delete his releases by clicking on each release and deleting it? Or is there a way for him to "move" his commits back to his repo? I found [THIS POST](https://stackoverflow.com/questions/37471740/how-to-copy-commits-from-one-git-repo-to-another) that speaks of `git cherry-pick`. Perhaps that is the "correct" way to go? – David Poindexter Jan 24 '18 at 15:40
-
@DavidPoindexter Deleting the release is possible (that won't delete the commits). And you can export those commits with cherry-pick, except you should use a range : https://stackoverflow.com/a/1994491/6309 – VonC Jan 24 '18 at 15:46
-
@WillStrohl see details above and this should do the trick. Thanks! – David Poindexter Jan 24 '18 at 16:19