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

Protect tags push #5595

New Issue
Closed
opened 2025-11-02 06:30:18 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 06:30:18 -06:00
Owner
Copy Link

Originally created by @micheelengronne on GitHub (Jun 19, 2020).

  • Gitea version (or commit ref): v1.12.0
  • Git version: 2.25.1
  • Operating system: ubuntu
  • 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

There is currently no way (AFAIK) to disable tag push via git cli. That means a user who can push code to a repository can always push tags.

Is there a way to protect tags creation the same way than branches and the same way than Github or Gitlab ?

Thanks.

Originally created by @micheelengronne on GitHub (Jun 19, 2020). - Gitea version (or commit ref): v1.12.0 - Git version: 2.25.1 - Operating system: ubuntu - Database (use `[x]`): - [X] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X] Not relevant - Log gist: ## Description There is currently no way (AFAIK) to disable tag push via git cli. That means a user who can push code to a repository can always push tags. Is there a way to protect tags creation the same way than branches and the same way than Github or Gitlab ? Thanks.
GiteaMirror added the type/proposal label 2025-11-02 06:30:18 -06:00
GiteaMirror commented 2025-11-02 06:30:19 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Dec 1, 2022):

This has been fixed by #15545

@lunny commented on GitHub (Dec 1, 2022): This has been fixed by #15545
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/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#5595
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?