source.dussan.org Git - gitea.git/commit

]> source.dussan.org Git - gitea.git/commit

author	zeripath <art27@cantab.net>
	Mon, 21 Oct 2019 08:21:45 +0000 (09:21 +0100)
committer	GitHub <noreply@github.com>
	Mon, 21 Oct 2019 08:21:45 +0000 (09:21 +0100)
commit	0bfe5eb10b1953cb1f85f7a7b6eb5f24724b8021
tree	8844040cf40b0f37c9457eade166a8bff1a91152	tree \| snapshot
parent	b1c1e1549b50bbd5929e2c4dd72a1dbf4b511b50	commit \| diff

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

13 files changed:

cmd/hook.go		diff \| blob \| history
cmd/serv.go		diff \| blob \| history
models/branches.go		diff \| blob \| history
models/migrations/migrations.go		diff \| blob \| history
models/migrations/v103.go	[new file with mode: 0644]	blob
models/update.go		diff \| blob \| history
modules/auth/repo_form.go		diff \| blob \| history
modules/private/hook.go		diff \| blob \| history
options/locale/locale_en-US.ini		diff \| blob \| history
routers/private/hook.go		diff \| blob \| history
routers/repo/http.go		diff \| blob \| history
routers/repo/setting_protected_branch.go		diff \| blob \| history
templates/repo/settings/protected_branch.tmpl		diff \| blob \| history

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD: https://github.com/go-gitea/gitea

RSS Atom