Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintaining connection with Github repository changing owners #1653

Open
noamross opened this issue Dec 3, 2018 · 9 comments
Open

Maintaining connection with Github repository changing owners #1653

noamross opened this issue Dec 3, 2018 · 9 comments

Comments

@noamross
Copy link

noamross commented Dec 3, 2018

I have a GitHub repo linked to Zenodo that has already had a couple of Zenodo releases. I want to transfer ownership of the GitHub repository to another GitHub user. Will Zenodo still uptake releases from that other repository? Can we switch the "watched" repository of a Zenodo record or direct a new repository to an existing record? Thanks!

@Glignos Glignos added the GitHub label Jul 5, 2019
@slint slint added this to To do in Asclepias/GitHub Sprint (Q3 2019) via automation Jul 8, 2019
@slint slint moved this from To do to GitHub Triage in Asclepias/GitHub Sprint (Q3 2019) Jul 8, 2019
@slint slint removed this from GitHub Triage in Asclepias/GitHub Sprint (Q3 2019) Jul 8, 2019
@feschmidt
Copy link

feschmidt commented Dec 2, 2019

Are there any plans to move further on this? I have a repository that had one release, then ownership was transferred and I now tried to make a second release, via github itself which worked fine.

However, it seems that while Zenodo recognizes a change of ownership on the user's github page (https://zenodo.org/account/settings/github/), clicking on the repository release page under https://zenodo.org/account/settings/github/repository/<new username>/<old repo name>, the repo and releases seem to still be linked to the old user, and the new releases return
{ "errors": "Unknown error occured." }

edit: This is regardless of whether the release is created by a tag or directly from a branch

@feschmidt
Copy link

and indeed the link to Create release... on the Zenodo github page still links to https://github.com/<old user>/<repo>/releases/new instead of https://github.com/<new user>/<repo>/releases/new

@MuellerSeb
Copy link

anything new on this? I am also planning to transfer a GitHub repo to another organization and don't want the Zenodo releases to break.

@sappelhoff
Copy link

I am also interested in this feature.

@samapriya
Copy link

Yeah stuck in the same situation here, I can create a release but since Zenodo cannot find the GitHub repo on my account anymore the release doesn't seem to be picked up by Zenodo

@benbovy
Copy link

benbovy commented Mar 9, 2021

FYI, I've just transferred a repo from my account to an organization (with Zenodo access enabled) on GitHub, logged in Zenodo and synced with GitHub, and it seems that Zenodo were able to automatically pick the new repo URL and keep the releases from the old repo URL (I haven't tried yet making a new release).

@RoyMudie
Copy link

@benbovy - don't suppose you've tried making a new release since the change to make sure this actually works now?

Facing the same problem. Leaving my current job and wanting to transfer ownership to a generic deparmental account. Obviously don't want to leave it broken :)

@benbovy
Copy link

benbovy commented Jun 23, 2021

@benbovy - don't suppose you've tried making a new release since the change to make sure this actually works now?

Not yet unfortunately, but I'll try to report here when we'll do so.

@cenouralm cenouralm removed the GitHub label Feb 1, 2023
@jsdodge
Copy link

jsdodge commented Apr 29, 2023

The GitHub documentation says that it automatically redirects the original URL to the transfer destination URL. This worked for me. I also found that I could update the URL in the Zenodo metadata without creating a new version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants