|
|
@@ -1,62 +1,91 @@
|
|
|
-# This workflow warns and then closes issues that have had no activity for a
|
|
|
+# This workflow warns and then closes issues that have had no activity for a
|
|
|
# specified amount of time. You can adjust the behavior by modifying this file.
|
|
|
# For more information, see:
|
|
|
# https://github.com/marketplace/actions/close-stale-issues
|
|
|
# https://github.com/actions/stale/blob/master/action.yml
|
|
|
# https://github.com/actions/stale
|
|
|
-
|
|
|
-# Disable yamlint truthy rule
|
|
|
-# https://yamllint.readthedocs.io/en/stable/rules.html#module-yamllint.rules.truthy
|
|
|
-# yamllint disable-line rule:truthy
|
|
|
-
|
|
|
---
|
|
|
-name: '180 Days Stale Issues Policy'
|
|
|
-on:
|
|
|
+name: 'Stale Issues Policy'
|
|
|
+on: # yamllint disable-line rule:truthy
|
|
|
schedule:
|
|
|
- - cron: "0 0 * * *"
|
|
|
+ - cron: '0 0 * * *' # Run at 00:00 UTC every day
|
|
|
+ workflow_dispatch:
|
|
|
+
|
|
|
permissions:
|
|
|
contents: read
|
|
|
+ issues: write # for actions/stale to close stale issues
|
|
|
|
|
|
jobs:
|
|
|
stale:
|
|
|
- permissions:
|
|
|
- issues: write # for actions/stale to close stale issues
|
|
|
runs-on: ubuntu-latest
|
|
|
steps:
|
|
|
- - name: '🧹 Mark & close stale issues'
|
|
|
- id: stale_issues
|
|
|
- uses: actions/stale@6f05e4244c9a0b2ed3401882b05d701dd0a7289b # v7
|
|
|
- with:
|
|
|
- repo-token: ${{ secrets.GITHUB_TOKEN }}
|
|
|
- days-before-issue-stale: 180
|
|
|
- days-before-close: 20
|
|
|
- operations-per-run: 300 # The maximum number of operations per run, used to control rate limiting
|
|
|
- stale-issue-label: ':status/automatic-stale'
|
|
|
- close-issue-label: ':status/automatic-closing'
|
|
|
- exempt-issue-labels: ':status/hold, :status/WIP, :type/enhancement'
|
|
|
- remove-stale-when-updated: true
|
|
|
- stale-issue-message: |
|
|
|
- 👋 Hello,
|
|
|
- There hasn't been any recent activity on this issue :sleeping:
|
|
|
- To keep our backlog manageable we have to clean old issues,
|
|
|
- as many of them have already been resolved with the latest updates.
|
|
|
-
|
|
|
- Please make sure to update to the latest [Logseq](https://logseq.com) version and
|
|
|
- Let us know us know if that solves the issue by adding a comment 💬
|
|
|
-
|
|
|
- This issue has been automatically marked as stale & will be closed in 20 days
|
|
|
- if no further activity occurs.
|
|
|
-
|
|
|
- Access additional 🌐 [Logseq](https://logseq.com) resources:
|
|
|
+ - name: '🧹 Mark & close stale issues'
|
|
|
+ id: stale_issues
|
|
|
+ uses: actions/stale@6f05e4244c9a0b2ed3401882b05d701dd0a7289b # v7
|
|
|
+ with:
|
|
|
+ repo-token: ${{ secrets.GITHUB_TOKEN }}
|
|
|
+ days-before-issue-stale: 180
|
|
|
+ days-before-close: 20
|
|
|
+ operations-per-run: 100 # max num of ops per run
|
|
|
+ stale-issue-label: ':status/automatic-stale'
|
|
|
+ close-issue-label: ':status/automatic-closing'
|
|
|
+ # trunk-ignore(yamllint/line-length)
|
|
|
+ exempt-issue-labels: ':status/hold, :status/WIP, :type/enhancement, type/can-be-reproduced, priority-A'
|
|
|
+ remove-stale-when-updated: true
|
|
|
+ stale-issue-message: |
|
|
|
+ Hi There! 👋
|
|
|
+
|
|
|
+ We haven't seen any activity on this issue in a while :sleeping:, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from [our website](https://logseq.com). If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!
|
|
|
+
|
|
|
+ If the issue has been resolved or is no longer relevant, that's great news! 🎉
|
|
|
+ We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.
|
|
|
+
|
|
|
+
|
|
|
+ Access additional [Logseq](https://logseq.com) 🚀 resources:
|
|
|
- **Forum**: https://discuss.logseq.com
|
|
|
- **Blog**: https://blog.logseq.com
|
|
|
- **Docs**: https://docs.logseq.com
|
|
|
-
|
|
|
- Feel free to inform us of any other **issues** you discover or **feature requests** that come to mind in the
|
|
|
- future. Pull Requests (PRs) are also always welcomed!
|
|
|
-
|
|
|
- Thank you for your contributions to Logseq :heart:!
|
|
|
-# close-issue-message: 'The issue has been automatically closed'
|
|
|
-
|
|
|
- - name: 'Print outputs'
|
|
|
- run: printf '%s\n' ${{ join(steps.stale.outputs.*, ',') }}
|
|
|
+
|
|
|
+ Thanks for your contributions to Logseq! If you have any other [**issues**](https://github.com/logseq/logseq/issues/new/choose) or [**feature requests**](https://discuss.logseq.com/c/feature-requests/), please don't hesitate to [let us know](https://github.com/logseq/logseq/issues/new/choose). We always welcome pull requests too!
|
|
|
+
|
|
|
+ - name: 'Print outputs'
|
|
|
+ run: |
|
|
|
+ for key in steps.stale_issues.outputs
|
|
|
+ do
|
|
|
+ printf '%s: %s\n' "${key}" "${steps.stale_issues.outputs[key]}"
|
|
|
+ done
|
|
|
+
|
|
|
+ - name: '🧹 Close stale awaiting response issues'
|
|
|
+ id: awaiting_issues
|
|
|
+ uses: actions/stale@6f05e4244c9a0b2ed3401882b05d701dd0a7289b # v7
|
|
|
+ with:
|
|
|
+ repo-token: ${{ secrets.GITHUB_TOKEN }}
|
|
|
+ days-before-issue-stale: 40
|
|
|
+ days-before-close: 20
|
|
|
+ operations-per-run: 30 # max num of ops per run
|
|
|
+ stale-issue-label: ':status/automatic-stale'
|
|
|
+ close-issue-label: ':status/automatic-closing'
|
|
|
+ only-labels: 'awaiting response'
|
|
|
+ remove-stale-when-updated: true
|
|
|
+ stale-issue-message: |
|
|
|
+ Hi There! 👋
|
|
|
+
|
|
|
+ We haven't seen any activity on this issue in a while :sleeping:, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from [our website](https://logseq.com). If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!
|
|
|
+
|
|
|
+ If the issue has been resolved or is no longer relevant, that's great news! 🎉
|
|
|
+ We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.
|
|
|
+
|
|
|
+
|
|
|
+ Access additional [Logseq](https://logseq.com) 🚀 resources:
|
|
|
+ - **Forum**: https://discuss.logseq.com
|
|
|
+ - **Blog**: https://blog.logseq.com
|
|
|
+ - **Docs**: https://docs.logseq.com
|
|
|
+
|
|
|
+ Thanks for your contributions to Logseq! If you have any other [**issues**](https://github.com/logseq/logseq/issues/new/choose) or [**feature requests**](https://discuss.logseq.com/c/feature-requests/), please don't hesitate to [let us know](https://github.com/logseq/logseq/issues/new/choose). We always welcome pull requests too!
|
|
|
+
|
|
|
+ - name: 'Print outputs'
|
|
|
+ run: |
|
|
|
+ for key in steps.awaiting_issues.outputs
|
|
|
+ do
|
|
|
+ printf '%s: %s\n' "${key}" "${steps.awaiting_issues.outputs[key]}"
|
|
|
+ done
|
Bad3r