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

Branch protection with required status check #14508

New Issue
Closed
opened 2025-11-02 11:14:52 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 11:14:52 -06:00
Owner
Copy Link

Originally created by @top-psi on GitHub (May 20, 2025).

Description

We have branch protection enabled with required status check set for "Lint yaml files / *".
Administrators must follow branch protection rules is enabled.

The required check failed on this PR. However, I was ​‌able to​‌ merge the PR.

https://gitea.psi.ch/HPCE/hashi-vault/pulls/12/commits
https://gitea.psi.ch/HPCE/hashi-vault/actions/runs/177/jobs/1

Gitea Version

1.23.8

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

RHEL 9

How are you running Gitea?

Docker

Database

PostgreSQL

Originally created by @top-psi on GitHub (May 20, 2025). ### Description We have branch protection enabled with required status check set for "Lint yaml files / *". Administrators must follow branch protection rules is enabled. The required check failed on this PR. However, I was ​‌able to​‌ merge the PR. https://gitea.psi.ch/HPCE/hashi-vault/pulls/12/commits https://gitea.psi.ch/HPCE/hashi-vault/actions/runs/177/jobs/1 ### Gitea Version 1.23.8 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System RHEL 9 ### How are you running Gitea? Docker ### Database PostgreSQL
GiteaMirror added the type/bug label 2025-11-02 11:14:52 -06:00
GiteaMirror commented 2025-11-02 11:14:53 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (May 26, 2025):

Can you post some screenshots? I suspect it's an automerge button bug.
It should be like this.

Image
@lunny commented on GitHub (May 26, 2025): Can you post some screenshots? I suspect it's an automerge button bug. It should be like this. <img width="992" alt="Image" src="https://github.com/user-attachments/assets/bf076d90-4776-48d2-8c7a-6cfa103396dd" />
GiteaMirror commented 2025-11-02 11:14:53 -06:00
Author
Owner
Copy Link

@pozsa commented on GitHub (May 26, 2025):

https://gitea.psi.ch/pozsa_k/merge-bug/pulls/2

Image

@pozsa commented on GitHub (May 26, 2025): https://gitea.psi.ch/pozsa_k/merge-bug/pulls/2 ![Image](https://github.com/user-attachments/assets/4eb0f6da-4705-4818-93da-50a2de8f65ef)
GiteaMirror commented 2025-11-02 11:14:53 -06:00
Author
Owner
Copy Link

@badhezi commented on GitHub (May 27, 2025):

can you share your branch protection rule configuration?
@pozsa

@badhezi commented on GitHub (May 27, 2025): can you share your branch protection rule configuration? @pozsa
GiteaMirror commented 2025-11-02 11:14:54 -06:00
Author
Owner
Copy Link

@pozsa commented on GitHub (May 30, 2025):

can you share your branch protection rule configuration? @pozsa

  • pattern: main
  • push: disable push
  • require signed commits: true
  • force push: disable force push
  • restrict approvals: false
  • dismiss stale approvals: true
  • enable status check: true
    • pattern: Lint yaml files / *
  • pr merge: enable merge
  • block merge on rejected reviews: true
  • block merge on official review requests: true
  • block merge if pr is outdated: true
  • admins must follow branch protection rules: true

@badhezi

@pozsa commented on GitHub (May 30, 2025): > can you share your branch protection rule configuration? [@pozsa](https://github.com/pozsa) - pattern: main - push: disable push - require signed commits: true - force push: disable force push - restrict approvals: false - dismiss stale approvals: true - enable status check: true - pattern: `Lint yaml files / *` - pr merge: enable merge - block merge on rejected reviews: true - block merge on official review requests: true - block merge if pr is outdated: true - admins must follow branch protection rules: true @badhezi
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/bug
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#14508
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?