forked from logseq/logseq
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathstale-issues.yml
91 lines (76 loc) · 5.23 KB
/
stale-issues.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
# 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
---
name: 'Stale Issues Policy'
on: # yamllint disable-line rule:truthy
schedule:
- 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:
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: 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
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