forked from forgejo/forgejo
Allow Protected Branches to Whitelist Deploy Keys (#8483)
Add an option to protected branches to add writing deploy keys to the whitelist for pushing. Please note this is technically a breaking change: previously if the owner of a repository was on the whitelist then any writing deploy key was effectively on the whitelist. This option will now need to be set if that is desired. Closes #8472 Details: * Allow Protected Branches to Whitelist Deploy Keys * Add migration * Ensure that IsDeployKey is set to false on the http pushes * add not null default false
This commit is contained in:
parent
b1c1e1549b
commit
0bfe5eb10b
13 changed files with 48 additions and 2 deletions
|
@ -1334,6 +1334,7 @@ settings.protect_this_branch = Enable Branch Protection
|
|||
settings.protect_this_branch_desc = Prevent deletion and disable any Git pushing to the branch.
|
||||
settings.protect_whitelist_committers = Enable Push Whitelist
|
||||
settings.protect_whitelist_committers_desc = Allow whitelisted users or teams to push to this branch (but not force push).
|
||||
settings.protect_whitelist_deploy_keys = Whitelist deploy keys with write access to push
|
||||
settings.protect_whitelist_users = Whitelisted users for pushing:
|
||||
settings.protect_whitelist_search_users = Search users…
|
||||
settings.protect_whitelist_teams = Whitelisted teams for pushing:
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue