Merge pull request #153 from chocolatey/repo-sync/github/default

(maint) synced file(s) with chocolatey/.github

.github/workflows/label-sync.yml

@@ -0,0 +1,24 @@
+name: Sync labels
+on:
+  workflow_dispatch:
+  schedule:
+    # Run at the end of the day (most likely UTC)
+    - cron: "0 0 * * *"
+
+jobs:
+  labels:
+    # We use ubuntu as the image, as it is typically faster and cheaper (on private repos).
+    runs-on: ubuntu-latest
+
+    steps:
+      # uncomment the uses line if additional configuration in the current
+      # repository is used.
+      #- uses: actions/[email protected]
+      - uses: EndBug/[email protected]
+        with:
+          config-file: |
+            https://raw.githubusercontent.com/chocolatey/.github/main/.github/labels.yml
+          request-token: ${{ secrets.SYNC_TOKEN }} # Used when getting the config files.
+          delete-other-labels: false # After initial run, and verification change this to true
+          dry-run: false
+          token: ${{ secrets.SYNC_TOKEN }} # Used when updating the labels on the repository.

.github/workflows/stale.yml

@@ -0,0 +1,48 @@
+name: 'Stale Issue and PR Cleanup'
+on:
+  workflow_dispatch:
+  schedule:
+    - cron: '0 4 * * *'
+
+permissions:
+  issues: write
+  pull-requests: write
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/[email protected]
+        id: stale
+        with:
+          days-before-stale: 30
+          days-before-close: 14
+          exempt-all-assignees: false
+          exempt-draft-pr: true
+          stale-issue-label: "Pending Closure"
+          stale-pr-label: 'Pending Closure'
+          only-labels: '0 - Waiting on User'
+          close-issue-label: "No Response / Stale"
+          close-pr-label: "No Response / Stale"
+          exempt-issue-labels: 'Security / CVE'
+          exempt-pr-labels: 'Security / CVE'
+          labels-to-remove-when-unstale: '0 - Wating on User,Pending closure'
+          stale-issue-message: |
+            Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
+            This issue will be closed in 14 days if it continues to be inactive.
+          close-issue-message: |
+            Dear contributor,
+
+            As this issue seems to have been inactive for quite some time now, it has been automatically closed.
+            If you feel this is a valid issue, please feel free to re-open the issue if / when a pull request
+            has been added.
+            Thank you for your contribution.
+
+          close-pr-message: |
+            Dear contributor,
+
+            As this PR seems to have been inactive for 30 days after changes / additional information
+            was requested, it has been automatically closed.
+            If you feel the changes are still valid, please re-open the PR once all changes or additional information
+            that was requested has been added.
+            Thank you for your contribution.