2021-10-04 18:43:08 +03:00
|
|
|
# Configuration for Repo Lockdown - https://github.com/dessant/repo-lockdown
|
|
|
|
|
|
|
|
|
|
name: 'Repo Lockdown'
|
|
|
|
|
|
|
|
|
|
on:
|
|
|
|
|
pull_request_target:
|
|
|
|
|
types: opened
|
|
|
|
|
|
|
|
|
|
permissions:
|
|
|
|
|
pull-requests: write
|
|
|
|
|
|
|
|
|
|
jobs:
|
|
|
|
|
action:
|
|
|
|
|
runs-on: ubuntu-latest
|
|
|
|
|
steps:
|
|
|
|
|
- uses: dessant/repo-lockdown@v2
|
|
|
|
|
with:
|
github: fix config mistake preventing repo lockdown commenting
The previous commit updated the repo lockdown config to the new
format:
commit 9b89cdb2a5064a87b8a7172fa1748d46aa37a9df
Author: Alex Bennée <alex.bennee@linaro.org>
Date: Mon Oct 4 16:43:08 2021 +0100
.github: move repo lockdown to the v2 configuration
Unfortunately the config key names used were wrong, resulting in
the repo lockdown throwing warnings:
Unexpected input(s) 'pull-comment', 'lock-pull', 'close-pull',
valid inputs are ['github-token', 'exclude-issue-created-before',
'exclude-issue-labels', 'issue-labels', 'issue-comment',
'skip-closed-issue-comment', 'close-issue', 'lock-issue',
'issue-lock-reason', 'exclude-pr-created-before', 'exclude-pr-labels',
'pr-labels', 'pr-comment', 'skip-closed-pr-comment', 'close-pr',
'lock-pr', 'pr-lock-reason', 'process-only', 'log-output']
It still locked down the pull requests, due to its default config,
but didn't leave the friendly message explaining why.
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2022-03-23 14:42:46 +03:00
|
|
|
pr-comment: |
|
2021-10-04 18:43:08 +03:00
|
|
|
Thank you for your interest in the QEMU project.
|
|
|
|
|
|
|
|
|
|
This repository is a read-only mirror of the project's repostories hosted
|
|
|
|
|
on https://gitlab.com/qemu-project/qemu.git.
|
|
|
|
|
The project does not process merge requests filed on GitHub.
|
|
|
|
|
|
|
|
|
|
QEMU welcomes contributions of code (either fixing bugs or adding new
|
|
|
|
|
functionality). However, we get a lot of patches, and so we have some
|
|
|
|
|
guidelines about contributing on the project website:
|
|
|
|
|
https://www.qemu.org/contribute/
|
github: fix config mistake preventing repo lockdown commenting
The previous commit updated the repo lockdown config to the new
format:
commit 9b89cdb2a5064a87b8a7172fa1748d46aa37a9df
Author: Alex Bennée <alex.bennee@linaro.org>
Date: Mon Oct 4 16:43:08 2021 +0100
.github: move repo lockdown to the v2 configuration
Unfortunately the config key names used were wrong, resulting in
the repo lockdown throwing warnings:
Unexpected input(s) 'pull-comment', 'lock-pull', 'close-pull',
valid inputs are ['github-token', 'exclude-issue-created-before',
'exclude-issue-labels', 'issue-labels', 'issue-comment',
'skip-closed-issue-comment', 'close-issue', 'lock-issue',
'issue-lock-reason', 'exclude-pr-created-before', 'exclude-pr-labels',
'pr-labels', 'pr-comment', 'skip-closed-pr-comment', 'close-pr',
'lock-pr', 'pr-lock-reason', 'process-only', 'log-output']
It still locked down the pull requests, due to its default config,
but didn't leave the friendly message explaining why.
Reviewed-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
2022-03-23 14:42:46 +03:00
|
|
|
lock-pr: true
|
|
|
|
|
close-pr: true
|