Push to mirror possible? #2914

New Issue

GiteaMirror · 2025-11-02T04:53:45-06:00

GiteaMirror commented

2025-11-02 04:53:45 -06:00

Originally created by @HaasJona on GitHub (Feb 14, 2019).

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 01c10a951b/cmd/serv.go (L214).

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.

Originally created by @HaasJona on GitHub (Feb 14, 2019). - Gitea version (or commit ref): 1.7.1 - Git version: 2.20.1 - Operating system: Linux - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description Pushing to mirror is currently impossible as there is a check in https://github.com/go-gitea/gitea/blob/01c10a951b9db0b9f020ef657ca71eb5e5882a84/cmd/serv.go#L214. 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.

GiteaMirror added the issue/duplicate label 2025-11-02 04:53:45 -06:00

GiteaMirror closed this issue

2025-11-02 04:53:45 -06:00

GiteaMirror commented

2025-11-02 04:53:47 -06:00

@HaasJona commented on GitHub (Mar 1, 2019):

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

@HaasJona commented on GitHub (Mar 1, 2019): I've commented out these checks locally and it seems to work fine.

GiteaMirror commented

2025-11-02 04:53:51 -06:00

@lunny commented on GitHub (Mar 1, 2019):

duplicated with #2280

@lunny commented on GitHub (Mar 1, 2019): duplicated with #2280

GiteaMirror commented

2025-11-02 04:53:53 -06:00

@stale[bot] commented on GitHub (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[bot] commented on GitHub (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.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#2914