You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of September 12th, only one user can "enable" archiving of a shared GitHub repository. If you try to enable archiving on a repository which was already enabled by another user, you will see the following message: "This repository is managed by another user of your GitHub organization."
This limitation was introduced so that only one hook is registered on GitHub repository. This way we can assure that GitHub releases result in only one Zenodo record, and most importantly in only one DOI being minted for the same content.
If you previously had access to a repository and now it's claimed by somebody else, please contact us on our support line (info@zenodo.org) so that we can resolve it and possibly transfer the ownership.
The text was updated successfully, but these errors were encountered:
Is it possible to transfer the "zenodo link" for an organization account? It is tied to one zenodo user. For an organization, I would like to take over (with the current linked user's approval of course) the release role but "this repository is managed by another user of this github organization" as the settings in zenodo tell me.
As of September 12th, only one user can "enable" archiving of a shared GitHub repository. If you try to enable archiving on a repository which was already enabled by another user, you will see the following message: "This repository is managed by another user of your GitHub organization."
This limitation was introduced so that only one hook is registered on GitHub repository. This way we can assure that GitHub releases result in only one Zenodo record, and most importantly in only one DOI being minted for the same content.
If you previously had access to a repository and now it's claimed by somebody else, please contact us on our support line (info@zenodo.org) so that we can resolve it and possibly transfer the ownership.
The text was updated successfully, but these errors were encountered: