github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-11 09:40:19 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Branch Protection Impossible For New Repositories #7283

New Issue
Closed
opened 2025-11-02 07:21:42 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 07:21:42 -06:00
Owner
Copy Link

Originally created by @muellert on GitHub (May 3, 2021).

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

Description

If I create a new repository, it is initially empty. In this case, I cannot set up branch protection, at least not via the UI.

Maybe templating could work around this?

...

Screenshots

20210503-gitea-repo-in-use
20210503-gitea-new-repo

Originally created by @muellert on GitHub (May 3, 2021). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> - Gitea version (or commit ref): 1.14.1 - Git version: n/a - Operating system: n/a <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) any, really - [ ] No - Log gist: <!-- It really is important to provide pertinent logs --> <!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems --> <!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini --> ## Description If I create a new repository, it is initially empty. In this case, I cannot set up branch protection, at least not via the UI. Maybe templating could work around this? ... ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** --> ![20210503-gitea-repo-in-use](https://user-images.githubusercontent.com/1183079/116870044-afdb4c80-ac09-11eb-9788-46b0e5fc2730.png) ![20210503-gitea-new-repo](https://user-images.githubusercontent.com/1183079/116870050-b36ed380-ac09-11eb-88ec-b43585c69e89.png)
GiteaMirror added the type/enhancement label 2025-11-02 07:21:42 -06:00
GiteaMirror commented 2025-11-02 07:21:43 -06:00
Author
Owner
Copy Link

@KN4CK3R commented on GitHub (May 3, 2021):

I noticed that too while implementing #15629 but did not add that restriction there. At the moment you must select an existing branch to enable branch protection. As an empty repository does not have branches that tab is stripped. #2529 might want this too.

@KN4CK3R commented on GitHub (May 3, 2021): I noticed that too while implementing #15629 but did not add that restriction there. At the moment you must select an existing branch to enable branch protection. As an empty repository does not have branches that tab is stripped. #2529 might want this too.
GiteaMirror commented 2025-11-02 07:21:43 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Oct 19, 2022):

Will also be fixed by #20825

@lunny commented on GitHub (Oct 19, 2022): Will also be fixed by #20825
GiteaMirror commented 2025-11-02 07:21:43 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 16, 2023):

Fixed by #20825

@lunny commented on GitHub (Jan 16, 2023): Fixed by #20825
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/enhancement
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#7283
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?