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
Forking a repository via the web UI currently requires visiting a /repo/fork/{{repoid}} URL. This makes it cumbersome to create a link that starts a fork, because the repository ID is only available via the API. While it is possible to create a link, doing so requires extra steps.
To make it easier to have a "Fork me!"-style links, introduce the /{username}/{repo}/fork route, which will start the forking process based on the repository in context instead.
This would bring gitea in line with Github's behavior too.
Screenshots
No response
The text was updated successfully, but these errors were encountered:
Feature Description
Forking a repository via the web UI currently requires visiting a /repo/fork/{{repoid}} URL. This makes it cumbersome to create a link that starts a fork, because the repository ID is only available via the API. While it is possible to create a link, doing so requires extra steps.
To make it easier to have a "Fork me!"-style links, introduce the /{username}/{repo}/fork route, which will start the forking process based on the repository in context instead.
This would bring gitea in line with Github's behavior too.
Screenshots
No response
The text was updated successfully, but these errors were encountered: