File tree 2 files changed +72
-0
lines changed
2 files changed +72
-0
lines changed Original file line number Diff line number Diff line change
1
+ name : Sync labels
2
+ on :
3
+ workflow_dispatch :
4
+ schedule :
5
+ # Run at the end of the day (most likely UTC)
6
+ - cron : " 0 0 * * *"
7
+
8
+ jobs :
9
+ labels :
10
+ # We use ubuntu as the image, as it is typically faster and cheaper (on private repos).
11
+ runs-on : ubuntu-latest
12
+
13
+ steps :
14
+ # uncomment the uses line if additional configuration in the current
15
+ # repository is used.
16
+ # - uses: actions/[email protected]
17
+
18
+ with :
19
+ config-file : |
20
+ https://raw.githubusercontent.com/chocolatey/.github/main/.github/labels.yml
21
+ request-token : ${{ secrets.SYNC_TOKEN }} # Used when getting the config files.
22
+ delete-other-labels : false # After initial run, and verification change this to true
23
+ dry-run : false
24
+ token : ${{ secrets.SYNC_TOKEN }} # Used when updating the labels on the repository.
Original file line number Diff line number Diff line change
1
+ name : ' Stale Issue and PR Cleanup'
2
+ on :
3
+ workflow_dispatch :
4
+ schedule :
5
+ - cron : ' 0 4 * * *'
6
+
7
+ permissions :
8
+ issues : write
9
+ pull-requests : write
10
+
11
+ jobs :
12
+ stale :
13
+ runs-on : ubuntu-latest
14
+ steps :
15
+
16
+ id : stale
17
+ with :
18
+ days-before-stale : 30
19
+ days-before-close : 14
20
+ exempt-all-assignees : false
21
+ exempt-draft-pr : true
22
+ stale-issue-label : " Pending Closure"
23
+ stale-pr-label : ' Pending Closure'
24
+ only-labels : ' 0 - Waiting on User'
25
+ close-issue-label : " No Response / Stale"
26
+ close-pr-label : " No Response / Stale"
27
+ exempt-issue-labels : ' Security / CVE'
28
+ exempt-pr-labels : ' Security / CVE'
29
+ labels-to-remove-when-unstale : ' 0 - Wating on User,Pending closure'
30
+ stale-issue-message : |
31
+ Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
32
+ This issue will be closed in 14 days if it continues to be inactive.
33
+ close-issue-message : |
34
+ Dear contributor,
35
+
36
+ As this issue seems to have been inactive for quite some time now, it has been automatically closed.
37
+ If you feel this is a valid issue, please feel free to re-open the issue if / when a pull request
38
+ has been added.
39
+ Thank you for your contribution.
40
+
41
+ close-pr-message : |
42
+ Dear contributor,
43
+
44
+ As this PR seems to have been inactive for 30 days after changes / additional information
45
+ was requested, it has been automatically closed.
46
+ If you feel the changes are still valid, please re-open the PR once all changes or additional information
47
+ that was requested has been added.
48
+ Thank you for your contribution.
You can’t perform that action at this time.
0 commit comments