[libvirt PATCH] Switch to new GitHub repo-lockdown configuration
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/lockdown.yml b/.github/lockdown.yml
deleted file mode 100644
index 7601a2a156..0000000000
--- a/.github/lockdown.yml
+++ /dev/null
@@ -1,38 +0,0 @@
-# Configuration for Repo Lockdown - https://github.com/dessant/repo-lockdown
-
-skipCreatedBefore: 2020-01-01
-
-# Close issues and pull requests
-close: true
-
-# Lock issues and pull requests
-lock: true
-
-# Optionally, specify configuration settings just for `issues` or `pulls`
-issues:
- comment: |
- Thank you for your interest in the libvirt project.
-
- Since this repository is a read-only mirror of the project's master repostory
hosted on GitLab, issues opened here are not processed.
-
- We kindly request that new issues are reported to
-
- https://gitlab.com/libvirt/libvirt/-/issues/new
-
- Thank you for your time and understanding.
-
-pulls:
- comment: |
- Thank you for your interest in the libvirt project.
-
- Since this repository is a read-only mirror of the project's master repostory
hosted on GitLab, merge requests opened here are not processed.
-
- We kindly request that contributors fork the project at
-
- https://gitlab.com/libvirt/libvirt/
-
- push changes to the fork, and then open a new merge request at
-
- https://gitlab.com/libvirt/libvirt/-/merge_requests/new
-
- Thank you for your time and understanding.
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
+
+jobs:
+ action:
+ runs-on: ubuntu-latest
+ steps:
+ - uses: dessant/repo-lockdown@v2
+ with:
+ issue-comment: |
+ Thank you for your interest in the libvirt project.
+
+ Since this repository is a read-only mirror of the project's master
+ repostory hosted on GitLab, issues opened here are not processed.
+
+ We kindly request that new issues are reported to
+
+ https://gitlab.com/libvirt/libvirt/-/issues/new
+
+ Thank you for your time and understanding.
+ lock-issue: true
+ close-issue: true
+ pr-comment: |
+ Thank you for your interest in the libvirt project.
+
+ Since this repository is a read-only mirror of the project's master
+ repostory hosted on GitLab, merge requests opened here are not
+ processed.
+
+ We kindly request that contributors fork the project at
+
+ https://gitlab.com/libvirt/libvirt/
+
+ push changes to the fork, and then open a new merge request at
+
+ https://gitlab.com/libvirt/libvirt/-/merge_requests/new
+
+ Thank you for your time and understanding.
+ lock-pr: true
+ close-pr: true
--
2.31.1