|
@@ -0,0 +1,31 @@
|
|
1
|
+#
|
|
2
|
+# check-pr.yml
|
|
3
|
+# Automatically close the PR if it's directed to a release branch
|
|
4
|
+#
|
|
5
|
+
|
|
6
|
+name: Check PR
|
|
7
|
+
|
|
8
|
+on:
|
|
9
|
+ pull_request:
|
|
10
|
+ branches:
|
|
11
|
+ - 1.0.x
|
|
12
|
+ - 1.1.x
|
|
13
|
+ - 2.0.x
|
|
14
|
+
|
|
15
|
+jobs:
|
|
16
|
+ check_pr:
|
|
17
|
+
|
|
18
|
+ runs-on: ubuntu-latest
|
|
19
|
+
|
|
20
|
+ steps:
|
|
21
|
+ - name: Comment on PR
|
|
22
|
+ uses: unsplash/comment-on-pr@master
|
|
23
|
+ env:
|
|
24
|
+ GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
25
|
+ with:
|
|
26
|
+ msg: "<p>Thanks for your contribution! \
|
|
27
|
+ Unfortunately we can't accept PRs directed at release branches. \
|
|
28
|
+ We make patches to the bugfix branches and only later do we push them out as releases. \
|
|
29
|
+ Please redo this PR starting with the `bugfix-2.0.x` branch and be careful to target `bugfix-2.0.x` when resubmitting the PR.</p> \
|
|
30
|
+ <p>It may help to set your fork's default branch to `bugfix-2.0.x`.</p> \
|
|
31
|
+ <p>See <a href='http://marlinfw.org/docs/development/getting_started_pull_requests.html' target='_blank'>this page</a> for full instructions.</p>"
|