Skip to content

Commit 253e207

Browse files
author
Christopher Doris
committed
update stale-bot messages
1 parent 423d38b commit 253e207

File tree

1 file changed

+34
-14
lines changed

1 file changed

+34
-14
lines changed

.github/workflows/stale.yaml

+34-14
Original file line numberDiff line numberDiff line change
@@ -14,20 +14,40 @@ jobs:
1414
with:
1515
exempt-all-milestones: true
1616
days-before-issue-stale: 30
17-
stale-issue-message: >
18-
This issue has been marked as stale because it has been open for 30 days with no
19-
activity. If the issue is still relevant then please leave a comment, or else it
20-
will be closed in 7 days.
17+
stale-issue-message: |
18+
Thank you for taking the time to report this issue!
19+
20+
However, it has been marked as stale because there has been no activity for 30
21+
days. As with many open source projects, the maintainers work for free and do
22+
not always have enough time to address all issues.
23+
24+
For questions, please check the documentation, other issues, or consider asking
25+
elsewhere such as Stack Overflow or Julia Discourse. For bugs, please try to
26+
find a fix yourself and consider opening a pull request. If you're still stuck,
27+
please leave a comment below.
28+
29+
If there is no further activity in 7 days, this issue will be automatically
30+
closed.
2131
days-before-pr-stale: 60
22-
stale-pr-message: >
23-
Thank you for your pull request. It has been marked as stale because it has been
24-
open for 60 days with no activity. If the PR is still relevant then please leave
25-
a comment, or else it will be closed in 30 days.
32+
stale-pr-message: |
33+
Thank you for taking the time to create this pull request!
34+
35+
However, it has been marked as stale because there has been no activity for 60
36+
days. As with many open source projects, the maintainers work for free and do
37+
not always have enough time to review all PRs.
38+
39+
Please ensure that all tests are passing, and that any new functionality has
40+
corresponding new tests (which should fail on old code and pass on new code).
41+
Also ensure any changes are documented or commented appropriately. If you're
42+
sure the PR is ready for review, please leave a comment below.
43+
44+
If there is no further activity in 7 days, this issue will be automatically
45+
closed.
2646
days-before-issue-close: 7
27-
close-issue-message: >
28-
This issue has been closed because it has been stale for 7 days. You can re-open
29-
it if it is still relevant.
47+
close-issue-message: |
48+
This issue has been closed because it has been stale for 7 days. If it is still
49+
relevant, please re-open it.
3050
days-before-pr-close: 30
31-
close-pr-message: >
32-
This PR has been closed because it has been stale for 30 days. You can re-open
33-
it if it is still relevant.
51+
close-pr-message: |
52+
This PR has been closed because it has been stale for 30 days. If it is still
53+
relevant, please re-open it.

0 commit comments

Comments
 (0)