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
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
The text was updated successfully, but these errors were encountered:
Add an API to update the remote repository path:
Additional notes
How currently repository renames are handled depends on the git source:
A way to automatically get the new repository path depends on the git source:
The text was updated successfully, but these errors were encountered: