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>		2024-07-05 18:21:56 +00:00
..
activity.go	Document possible action types for the user activity feed API (#31196)	2024-06-03 13:40:48 +00:00
activitypub.go
admin_user.go	chore(api): support ignore password if login source type is LDAP for creating user API (#28491)	2023-12-19 02:32:45 +00:00
attachment.go
commit_status_test.go
commit_status.go
cron.go
doc.go
fork.go
git_blob.go
git_hook.go
hook.go
issue_comment.go
issue_label.go	Support using label names when changing issue labels (#30943)	2024-05-13 04:28:53 +00:00
issue_milestone.go
issue_reaction.go
issue_stopwatch.go
issue_test.go
issue_tracked_time.go
issue.go	Make gitea webhooks openproject compatible (#28435)	2024-05-26 04:08:13 +00:00
lfs_lock.go
mirror.go
miscellaneous.go	Fix missing images in editor preview due to wrong links (#31299)	2024-06-17 14:16:14 +08:00
nodeinfo.go
notifications.go
org_member.go
org_team.go	Increase max length of org team names from 30 to 255 characters (#31410)	2024-06-19 10:36:09 -04:00
org.go
package.go
pull_review.go
pull.go	Make gitea webhooks openproject compatible (#28435)	2024-05-26 04:08:13 +00:00
release.go
repo_actions.go	Add API endpoints for getting action jobs status (#26673)	2024-05-01 09:40:23 +08:00
repo_branch.go	Allow force push to protected branches (#28086)	2024-07-05 18:21:56 +00:00
repo_collaborator.go
repo_commit.go
repo_compare.go	feat(api): implement branch/commit comparison API (#30349)	2024-04-16 11:45:04 +08:00
repo_file.go
repo_key.go
repo_note.go
repo_refs.go
repo_tag.go	Add tag protection via rest api #17862 (#31295)	2024-06-14 18:56:10 +02:00
repo_topic.go
repo_tree.go
repo_watch.go
repo_wiki.go
repo.go	Add topics for repository API (#31127)	2024-05-28 10:03:54 +00:00
secret.go
settings.go
status.go
task.go
user_app.go
user_email.go
user_gpgkey.go
user_key.go
user.go	Make gitea webhooks openproject compatible (#28435)	2024-05-26 04:08:13 +00:00
variable.go	Add API for Variables (#29520)	2024-03-28 20:40:35 +00:00
visible_type.go