github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Restrict mirroring settings to admins #10467

New Issue
Open
opened 2025-11-02 09:08:12 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 09:08:12 -06:00
Owner
Copy Link

Originally created by @fpoirotte on GitHub (Mar 21, 2023).

Feature Description

Hi,

We host several repositories for our own usage as well as for various consumers.
As site administrators, we would like to mirror some remote repositories while preventing regular users from setting up their own mirroring configuration.

Right now, best workaround we found was to enable mirrors globally, but to use DISABLE_NEW_PULL and DISABLE_NEW_PUSH to control when new mirrors can be defined.

This is tedious (disable DISABLE_NEW_*, add the new mirror using the UI, then re-enable DISABLE_NEW_* to prevent other users from adding their own configuration).
This is also not a perfect solution (while we are setting up the new mirror, regular users may still have time to add their own configuration).

Would it be possible to only allow site administrators to configure new mirrors?

Regards,
François

Screenshots

No response

Originally created by @fpoirotte on GitHub (Mar 21, 2023). ### Feature Description Hi, We host several repositories for our own usage as well as for various consumers. As site administrators, we would like to mirror some remote repositories while preventing regular users from setting up their own mirroring configuration. Right now, best workaround we found was to enable mirrors globally, but to use `DISABLE_NEW_PULL` and `DISABLE_NEW_PUSH` to control when new mirrors can be defined. This is tedious (disable `DISABLE_NEW_*`, add the new mirror using the UI, then re-enable `DISABLE_NEW_*` to prevent other users from adding their own configuration). This is also not a perfect solution (while we are setting up the new mirror, regular users may still have time to add their own configuration). Would it be possible to only allow site administrators to configure new mirrors? Regards, François ### Screenshots _No response_
GiteaMirror added the type/proposaltype/feature labels 2025-11-02 09:08:12 -06:00
GiteaMirror commented 2025-11-02 09:08:12 -06:00
Author
Owner
Copy Link

@poVoq commented on GitHub (Mar 24, 2023):

Restricting it by team membership would be also interesting.

@poVoq commented on GitHub (Mar 24, 2023): Restricting it by team membership would be also interesting.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/feature type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#10467
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?