Skip to content
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

Feature Request: Protect tags #15545

Closed
2 of 6 tasks
eNBeWe opened this issue Apr 19, 2021 · 2 comments · Fixed by #15629
Closed
2 of 6 tasks

Feature Request: Protect tags #15545

eNBeWe opened this issue Apr 19, 2021 · 2 comments · Fixed by #15629
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@eNBeWe
Copy link

eNBeWe commented Apr 19, 2021

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

Description

We are currently migrating towards using Gitea as our company Git server. In the process we stumbled upon the fact that tags are not protectable in Gitea. We would like to have some way to restrict write access to tags through the UI.
At the moment we might be able to help us with re-enabling Git-Hooks, but this doesn't give us control over permissions etc.

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Apr 19, 2021
@SuperOok
Copy link

As there were clarification questions, this requests wants the following:

  • add a configuring option in the UI
  • make it possible to configure specific tags
  • you can add restrictions on users who can create, update, delete the named tags

Such a feature exists already for branch protection, but in gitea not for tag protection.
It exists in gitlab: https://docs.gitlab.com/ee/user/project/protected_tags.html
There wildcards can be used to specified tags or tag-families which should be configured with permissions.

Example usage: A release tag like release_1.0.05 is set by a specific role or person and is only allowed to be updated or deleted by that role or person.

@KN4CK3R
Copy link
Member

KN4CK3R commented Apr 26, 2021

I added this with #15629.

@go-gitea go-gitea locked and limited conversation to collaborators Oct 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants