[libvirt PATCH] Switch to new GitHub repo-lockdown configuration
Daniel P. Berrangé
berrange at redhat.com
Wed Oct 20 11:06:36 UTC 2021
On Wed, Oct 20, 2021 at 01:05:20PM +0200, Ján Tomko wrote:
> 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 at 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 at redhat.com>
>
> Jano
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
More information about the libvir-list
mailing list