|
@@ -1,6 +1,6 @@
|
1
|
1
|
#
|
2
|
|
-# comment-pr.yml
|
3
|
|
-# Add a comment to any PR directed to a release branch
|
|
2
|
+# check-pr.yml
|
|
3
|
+# Close PRs directed at release branches
|
4
|
4
|
#
|
5
|
5
|
|
6
|
6
|
name: PR Bad Target
|
|
@@ -19,9 +19,14 @@ jobs:
|
19
|
19
|
runs-on: ubuntu-latest
|
20
|
20
|
|
21
|
21
|
steps:
|
22
|
|
- - uses: actions/checkout@v1
|
23
|
|
- - uses: harupy/comment-on-pr@master
|
24
|
|
- env:
|
25
|
|
- GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
26
|
|
- with:
|
27
|
|
- filename: bad-target.md
|
|
22
|
+ - uses: peter-evans/close-pull@v1
|
|
23
|
+ with:
|
|
24
|
+ delete-branch: false
|
|
25
|
+ comment: >
|
|
26
|
+ Thanks for your contribution! Unfortunately we can't accept PRs directed at release branches. We make patches to the bugfix branches and only later do we push them out as releases.
|
|
27
|
+
|
|
28
|
+ 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.
|
|
29
|
+
|
|
30
|
+ It may help to set your fork's default branch to `bugfix-2.0.x`.
|
|
31
|
+
|
|
32
|
+ See [this page](http://marlinfw.org/docs/development/getting_started_pull_requests.html) for full instructions.
|