Git with a cup of tea, painless self-hosted git service Mirror for internal git.with.parts use https://git.with.parts

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Henry Goodman 12cb1d2998 Allow force push to protected branches (#28086) ... Fixes #22722 ### Problem Currently, it is not possible to force push to a branch with branch protection rules in place. There are often times where this is necessary (CI workflows/administrative tasks etc). The current workaround is to rename/remove the branch protection, perform the force push, and then reinstate the protections. ### Solution Provide an additional section in the branch protection rules to allow users to specify which users with push access can also force push to the branch. The default value of the rule will be set to `Disabled`, and the UI is intuitive and very similar to the `Push` section. It is worth noting in this implementation that allowing force push does not override regular push access, and both will need to be enabled for a user to force push. This applies to manual force push to a remote, and also in Gitea UI updating a PR by rebase (which requires force push) This modifies the `BranchProtection` API structs to add: - `enable_force_push bool` - `enable_force_push_whitelist bool` - `force_push_whitelist_usernames string[]` - `force_push_whitelist_teams string[]` - `force_push_whitelist_deploy_keys bool` ### Updated Branch Protection UI: <img width="943" alt="image" src="https://github.com/go-gitea/gitea/assets/79623665/7491899c-d816-45d5-be84-8512abd156bf"> ### Pull Request `Update branch by Rebase` option enabled with source branch `test` being a protected branch:  <img width="1038" alt="image" src="https://github.com/go-gitea/gitea/assets/79623665/57ead13e-9006-459f-b83c-7079e6f4c654"> --------- Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>		5 months ago
..
base	Enable more `revive` linter rules (#30608)	7 months ago
fixtures	Remove If Exist check on migration for mssql because that syntax required SQL server 2016 (#30894)	7 months ago
v1_6	Enable more `revive` linter rules (#30608)	7 months ago
v1_7	Rename `Sync2` -> `Sync` (#26479)	1 year ago
v1_8	Rename `Sync2` -> `Sync` (#26479)	1 year ago
v1_9	Enable more `revive` linter rules (#30608)	7 months ago
v1_10	Rename `Sync2` -> `Sync` (#26479)	1 year ago
v1_11	Enable more `revive` linter rules (#30608)	7 months ago
v1_12	Rename `Sync2` -> `Sync` (#26479)	1 year ago
v1_13	Rename `Sync2` -> `Sync` (#26479)	1 year ago
v1_14	Use `crypto/sha256` (#29386)	9 months ago
v1_15	Rename `Sync2` -> `Sync` (#26479)	1 year ago
v1_16	Fix some bug on migrations (#30647)	7 months ago
v1_17	Update misspell to 0.5.1 and add `misspellings.csv` (#30573)	7 months ago
v1_18	Fix wrong table name (#30557)	7 months ago
v1_19	Rename `Sync2` -> `Sync` (#26479)	1 year ago
v1_20	Enable more `revive` linter rules (#30608)	7 months ago
v1_21	handle repository.size column being NULL in migration v263 (#28336)	12 months ago
v1_22	Fix the possible migration failure on 286 with postgres 16 (#31209)	6 months ago
v1_23	Allow force push to protected branches (#28086)	5 months ago
migrations.go	Allow force push to protected branches (#28086)	5 months ago