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.

Sign up for GitHub

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

Jump to bottom

Handle remote repository rename #49

Open

sgotti opened this issue Jul 13, 2019 · 0 comments

Labels

Member

sgotti commented Jul 13, 2019

Add an API to update the remote repository path:

Manual (entering new path)
Automaitic (fetch remote repo info using the remote repo id and update the path with the new received path)

Additional notes

How currently repository renames are handled depends on the git source:

github: implements redirects for web and git urls. So everything should work in agola also after a rename until a new repo with the previous name is created (this will override/remove the automatic redirect)
gitea: doesn't provide a github like redirect mechanism. So after a rename agola will break since git clones won't work
gitlab: to investigate

A way to automatically get the new repository path depends on the git source:

github: has an "hidden" but reported as stable api to get a repository by id
gitea: currently no way to get a repo by id
gitlab: has a stable api to get a repo by id

sgotti added the enhancement label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment