On a Monday in 2021, Daniel P. Berrangé wrote:
> The repo-lockdown service used to run as a bot outside GitHub, but has
> now switched to using the GitHub Actions workflow framework. This
> requires use of a new configuration file.
>
> Signed-off-by: Daniel P. Berrangé <berrange(a)redhat.com>
> ---
> .github/lockdown.yml | 38 -------------------------
> .github/workflows/lockdown.yml | 51 ++++++++++++++++++++++++++++++++++
> 2 files changed, 51 insertions(+), 38 deletions(-)
> delete mode 100644 .github/lockdown.yml
> create mode 100644 .github/workflows/lockdown.yml
>
> diff --git a/.github/workflows/lockdown.yml b/.github/workflows/lockdown.yml
> new file mode 100644
> index 0000000000..f7646d9bde
> --- /dev/null
> +++ b/.github/workflows/lockdown.yml
> @@ -0,0 +1,51 @@
> +---
> +# Configuration for Repo Lockdown -
https://github.com/dessant/repo-lockdown
> +
> +name: 'Repo Lockdown'
> +
> +on:
> + issues:
> + types: opened
> + pull_request_target:
> + types: opened
> +
> +permissions:
> + pull-requests: write
> +
This also needs
issues: write
Ahhhhhhhhhhhhhhhh! This explains why I was going mad yesterday when
testing it and failing on issues.
> +jobs:
> + action:
> + runs-on: ubuntu-latest
> + steps:
Reviewed-by: Ján Tomko <jtomko(a)redhat.com>
Jano