Skip to content

Push to mirror possible? #6071

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.

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

Closed
2 of 7 tasks
HaasJona opened this issue Feb 14, 2019 · 3 comments
Closed
2 of 7 tasks

Push to mirror possible? #6071

HaasJona opened this issue Feb 14, 2019 · 3 comments
Labels
issue/duplicate The issue has already been reported.

Comments

@HaasJona
Copy link

  • Gitea version (or commit ref): 1.7.1
  • Git version: 2.20.1
  • Operating system: Linux
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Pushing to mirror is currently impossible as there is a check in

if requestedMode > models.AccessModeRead && repo.IsMirror {
.

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.

@HaasJona HaasJona reopened this Mar 1, 2019
@HaasJona
Copy link
Author

HaasJona commented Mar 1, 2019

I've commented out these checks locally and it seems to work fine.

@lunny
Copy link
Member

lunny commented Mar 1, 2019

duplicated with #2280

@stale
Copy link

stale bot commented Apr 30, 2019

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.

@stale stale bot added the issue/stale label Apr 30, 2019
@lunny lunny added the issue/duplicate The issue has already been reported. label May 6, 2019
@stale stale bot removed the issue/stale label May 6, 2019
@lunny lunny closed this as completed May 6, 2019
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/duplicate The issue has already been reported.
Projects
None yet
Development

No branches or pull requests

2 participants