Explorar el Código

👔 Move actions to default branch

Scott Lahteine hace 2 años
padre
commit
0a8672ae6c

+ 16
- 6
.github/pull_request_template.md Ver fichero

@@ -1,23 +1,33 @@
1
-### Requirements
1
+<!--
2
+
3
+Submitting a Pull Request
4
+
5
+- Please fill out all sections of this form. You can delete the helpful comments.
6
+- Pull Requests without clear information will take longer and may even be rejected.
7
+- We get a high volume of submissions so please be patient during review.
2 8
 
3
-* Filling out this template is required. Pull Requests without a clear description may be closed at the maintainers' discretion.
9
+-->
4 10
 
5 11
 ### Description
6 12
 
7 13
 <!--
8 14
 
9
-We must be able to understand your proposed change from this description. If we can't understand what the code will do from this description, the Pull Request may be closed at the maintainers' discretion. Keep in mind that the maintainer reviewing this PR may not be familiar with or have worked with the code recently, so please walk us through the concepts.
15
+Clearly describe the submitted changes with lots of details. Include images where helpful. Initial reviewers may not be familiar with the subject, so be as thorough as possible. You can use MarkDown syntax to improve readability with bullet lists, code blocks, and so on. PREVIEW and fix up formatting before submitting.
10 16
 
11 17
 -->
12 18
 
19
+### Requirements
20
+
21
+<!-- Does this PR require a specific board, LCD, etc.? -->
22
+
13 23
 ### Benefits
14 24
 
15
-<!-- What does this fix or improve? -->
25
+<!-- What does this PR fix or improve? -->
16 26
 
17 27
 ### Configurations
18 28
 
19
-<!-- Attach any Configuration.h, Configuration_adv.h, or platformio.ini files needed to compile/test your Pull Request. -->
29
+<!-- Attach Configurations ZIP and any other files needed to test this PR. -->
20 30
 
21 31
 ### Related Issues
22 32
 
23
-<!-- Whether this fixes a bug or fulfills a feature request, please list any related Issues here. -->
33
+<!-- Does this PR fix a bug or fulfill a Feature Request? Link related Issues here. -->

+ 39
- 0
.github/workflows/bump-date.yml Ver fichero

@@ -0,0 +1,39 @@
1
+#
2
+# bump-date.yml
3
+# Bump the distribution date once per day
4
+#
5
+
6
+name: Bump Distribution Date
7
+
8
+on:
9
+  schedule:
10
+    - cron: '0 */6 * * *'
11
+
12
+jobs:
13
+  bump_date:
14
+    name: Bump Distribution Date
15
+    if: github.repository == 'MarlinFirmware/Marlin'
16
+
17
+    runs-on: ubuntu-latest
18
+
19
+    steps:
20
+
21
+    - name: Check out bugfix-2.0.x
22
+      uses: actions/checkout@v2
23
+      with:
24
+        ref: bugfix-2.0.x
25
+
26
+    - name: Bump Distribution Date
27
+      run: |
28
+        # Inline Bump Script
29
+        if [[ ! "$( git log -1 --pretty=%B )" =~ ^\[cron\] ]]; then
30
+          DIST=$( date +"%Y-%m-%d" )
31
+          eval "sed -E -i 's/(#define +STRING_DISTRIBUTION_DATE) .*$/\1 \"$DIST\"/g' Marlin/src/inc/Version.h" && \
32
+          eval "sed -E -i 's/(#define +STRING_DISTRIBUTION_DATE) .*$/\1 \"$DIST\"/g' Marlin/Version.h" && \
33
+          git config user.name "${GITHUB_ACTOR}" && \
34
+          git config user.email "${GITHUB_ACTOR}@users.noreply.github.com" && \
35
+          git add . && \
36
+          git commit -m "[cron] Bump distribution date ($DIST)" && \
37
+          git push
38
+        fi
39
+        exit 0

+ 33
- 0
.github/workflows/check-pr.yml Ver fichero

@@ -0,0 +1,33 @@
1
+#
2
+# check-pr.yml
3
+# Close PRs directed at release branches
4
+#
5
+
6
+name: PR Bad Target
7
+
8
+on:
9
+  pull_request_target:
10
+    types: [opened]
11
+    branches:
12
+    - 1.0.x
13
+    - 1.1.x
14
+    - 2.0.x
15
+
16
+jobs:
17
+  bad_target:
18
+    name: PR Bad Target
19
+    if: github.repository == 'MarlinFirmware/Marlin'
20
+
21
+    runs-on: ubuntu-latest
22
+
23
+    steps:
24
+    - uses: superbrothers/close-pull-request@v3
25
+      with:
26
+        comment: >
27
+          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.
28
+
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.
30
+
31
+          It may help to set your fork's default branch to `bugfix-2.0.x`.
32
+
33
+          See [this page](http://marlinfw.org/docs/development/getting_started_pull_requests.html) for full instructions.

+ 39
- 0
.github/workflows/clean-closed.yml Ver fichero

@@ -0,0 +1,39 @@
1
+#
2
+# clean-closed.yml
3
+# Remove obsolete labels when an Issue or PR is closed
4
+#
5
+
6
+name: Clean Closed
7
+
8
+on:
9
+  pull_request:
10
+    types: [closed]
11
+  issues:
12
+    types: [closed]
13
+
14
+jobs:
15
+  remove_label:
16
+    runs-on: ubuntu-latest
17
+
18
+    strategy:
19
+      matrix:
20
+        label:
21
+          - "S: Don't Merge"
22
+          - "S: Hold for 2.1"
23
+          - "S: Please Merge"
24
+          - "S: Please Test"
25
+          - "help wanted"
26
+          - "Needs: Discussion"
27
+          - "Needs: Documentation"
28
+          - "Needs: More Data"
29
+          - "Needs: Patch"
30
+          - "Needs: Testing"
31
+          - "Needs: Work"
32
+
33
+    steps:
34
+      - uses: actions/checkout@v2
35
+      - name: Remove Labels
36
+        uses: actions-ecosystem/action-remove-labels@v1
37
+        with:
38
+          github_token: ${{ github.token }}
39
+          labels: ${{ matrix.label }}

+ 28
- 0
.github/workflows/close-stale.yml Ver fichero

@@ -0,0 +1,28 @@
1
+#
2
+# close-stale.yml
3
+# Close open issues after a period of inactivity
4
+#
5
+
6
+name: Close Stale Issues
7
+
8
+on:
9
+  schedule:
10
+  - cron: "22 1 * * *"
11
+
12
+jobs:
13
+  stale:
14
+    name: Close Stale Issues
15
+    if: github.repository == 'MarlinFirmware/Marlin'
16
+
17
+    runs-on: ubuntu-latest
18
+
19
+    steps:
20
+    - uses: actions/stale@v3
21
+      with:
22
+        repo-token: ${{ secrets.GITHUB_TOKEN }}
23
+        stale-issue-message: 'This issue has had no activity in the last 60 days. Please add a reply if you want to keep this issue active, otherwise it will be automatically closed within 10 days.'
24
+        days-before-stale: 60
25
+        days-before-close: 10
26
+        stale-issue-label: 'stale-closing-soon'
27
+        exempt-all-assignees: true
28
+        exempt-issue-labels: 'Bug: Confirmed !,T: Feature Request,Needs: Discussion,Needs: Documentation,Needs: Patch,Needs: Work,Needs: Testing,help wanted,no-locking'

+ 32
- 0
.github/workflows/lock-closed.yml Ver fichero

@@ -0,0 +1,32 @@
1
+#
2
+# lock-closed.yml
3
+# Lock closed issues after a period of inactivity
4
+#
5
+
6
+name: Lock Closed Issues
7
+
8
+on:
9
+  schedule:
10
+    - cron: '0 1/13 * * *'
11
+
12
+jobs:
13
+  lock:
14
+    name: Lock Closed Issues
15
+    if: github.repository == 'MarlinFirmware/Marlin'
16
+
17
+    runs-on: ubuntu-latest
18
+
19
+    steps:
20
+    - uses: dessant/lock-threads@v2
21
+      with:
22
+        github-token: ${{ github.token }}
23
+        process-only: 'issues'
24
+        issue-lock-inactive-days: '60'
25
+        issue-exclude-created-before: ''
26
+        issue-exclude-labels: 'no-locking'
27
+        issue-lock-labels: ''
28
+        issue-lock-comment: >
29
+          This issue has been automatically locked since there
30
+          has not been any recent activity after it was closed.
31
+          Please open a new issue for related bugs.
32
+        issue-lock-reason: ''

+ 22
- 0
.github/workflows/unlock-reopened.yml Ver fichero

@@ -0,0 +1,22 @@
1
+#
2
+# unlock-reopened.yml
3
+# Unlock an issue whenever it is re-opened
4
+#
5
+
6
+name: "Unlock reopened issue"
7
+
8
+on:
9
+  issues:
10
+    types: [reopened]
11
+
12
+jobs:
13
+  unlock:
14
+    name: Unlock Reopened
15
+    if: github.repository == 'MarlinFirmware/Marlin'
16
+
17
+    runs-on: ubuntu-latest
18
+
19
+    steps:
20
+    - uses: OSDKDev/unlock-issues@v1.1
21
+      with:
22
+        repo-token: "${{ secrets.GITHUB_TOKEN }}"

Loading…
Cancelar
Guardar