So this is one of the main issues I find while using OneDev, is the lack of repository management, well this may not be the best thing to call it, but I will explain what I mean.

First up, as discussed in issue #1085, I have issues with keeping the forks syncronised, and using CI/CD or PR manually is quite honestly a horrible way to do this, adding a button to the repository "sync with parent" which simply pushes the parent changes to master/main into the fork, I do not believe this will be particularly difficult to implement, but it is really something which holds OneDev back.

This links onto my next point, the ability to mirror git repositories automatically to OneDev, this can be from other OneDev instances, gitea, a generic http git endpoint, github, gitlab etc

Adding a "import" feature to the new repository would allow for:

• Better migrations
• Ability to periodically update mirrored repositories automatically without CI/CD (this can be scheduled to be done automatically by the OneDev instance at midnight every day)

Part one is high priority as it will make contributing to OneDev 100x easier, second feature would be nice to have but is low priority.