github: Update lockdown message when opening a PR

The message that's thrown at users when they try to open a pull
request on github suggests opening the MR on gitlab instead.
While this works for other libvirt subprojects, for the main
libvirt.git we still use e-mail workflow. Update the message to
reflect this fact.

Signed-off-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: Martin Kletzander <mkletzan@redhat.com>

diff --git a/.github/workflows/lockdown.yml b/.github/workflows/lockdown.yml
index 74931a2944cecee207a21fadda9ed1ee5edbab94..91d2cc20065dad5dedfb75ceffaaf7f47d27af25 100644 (file)
--- a/.github/workflows/lockdown.yml
+++ b/.github/workflows/lockdown.yml
@@ -23,7 +23,7 @@ jobs:
             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.
+            repository hosted on GitLab, issues opened here are not processed.
 
             We kindly request that new issues are reported to
 
@@ -36,16 +36,13 @@ jobs:
             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
+            repository hosted on GitLab, merge requests opened here are not
             processed.
 
-            We kindly request that contributors fork the project at
+            For main libvirt.git repository all patch review and discussion
+            only occurs on the devel mailing list.
 
-              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
+              https://libvirt.org/submitting-patches.html
 
             Thank you for your time and understanding.
           lock-pr: true