Extend Gated Feature with an Allow/Block List

[6543]

extend feature added (back) in #51

---

ref: https://codeberg.org/Codeberg/Community/issues/428#issuecomment-195258
ref: #193

[6543]

#1969 created a dedicated file to handle new cases in it :)

[xoxys]

Do you already have some ideas in mind on how this should be implemented? I would like to work on this, as at least for me, it gets annoying very fast 🙈

A repo setting to configure a list of authors that can be checked in https://github.com/woodpecker-ci/woodpecker/blob/main/server/pipeline/gated.go#L20

[6543]

well there are ideas like:

• allow listing: if a user has X accepted pipelines it gets accepted automatically
• allow listing: if the pipeline config already did run allow it automatically
• deny listing: if pipeline target branch X make it gated ...

so basically there are rules and you could have a allow- or a deny- block-list

[xoxys]

Would it make sense to integrate open policy agent for stuff like this? We could allow admins to write the own policies. We could also make use of it in e.g. extensions as proposed in #915

[anbraten]

opa is a great tool, but for WP it feels to me it would add to much complexity.