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
Is this a hard technical limitation or is it only forbidden because it is slightly dangerous? Do you think this can be enabled?
Usecase: Create a up-to-date mirror of the official source code repository, but push experimental/internal features into a private and mirroring gitea instance first, which is also used by CI runners and so on.
Branches like master would always be up-to-date with upsteam because of the mirroring and would be protected by local pushes, while you could push feature-branches that are not upstream.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
[x]
):Description
Pushing to mirror is currently impossible as there is a check in
gitea/cmd/serv.go
Line 214 in 01c10a9
Is this a hard technical limitation or is it only forbidden because it is slightly dangerous? Do you think this can be enabled?
Usecase: Create a up-to-date mirror of the official source code repository, but push experimental/internal features into a private and mirroring gitea instance first, which is also used by CI runners and so on.
Branches like master would always be up-to-date with upsteam because of the mirroring and would be protected by local pushes, while you could push feature-branches that are not upstream.
The text was updated successfully, but these errors were encountered: