-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
Branch protection, can still be pushed #24373
Comments
Are you admin? |
yes |
Update: maybe I read it wrong. |
I cannot reproduce that. I don't think the site admin can bypass that rule. |
Upgrade from previous version to v1.19.1 |
Upgrade from previous version to v1.19.1 |
What's your app.ini config / local git repo config (remote) / push command? and what's the response? And one more question, can you reproduce it with a new / clear installation? |
|
Any progress? |
The latest version is fine, but the upgrade from the original version will not work. |
Could you run |
If you create a new repo in your old instance, does its branch protection work? |
Tried, invalid |
If you have tried ps: does protection work for the push over https (not ssh)? if https works, then the problem is highly likely related the ssh part. |
Use http, invalid |
Those logs will not affect anything. |
I am having the same issue with Gitea version 1.19.3. Using docker.
|
Which version did you upgrade to v1.19.1 from? |
It may be gradually upgraded from v1.14.8, basically every version will be upgraded, but it is not clear which version to start from. This can be used well. |
We close issues that need feedback from the author if there were no new comments for a month. 🍵 |
Description
Branch protection, can still be pushed
Gitea Version
1.19.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
docker
How are you running Gitea?
docker
Database
MySQL
The text was updated successfully, but these errors were encountered: