Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 471cb64

Browse files
Replace the stale both with more advanced version (#48)
1 parent 11f4b6a commit 471cb64

File tree

1 file changed

+27
-12
lines changed

1 file changed

+27
-12
lines changed

‎.github/no-response.yml

Lines changed: 27 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,30 @@
1-
# Configuration for probot-no-response - https://github.com/probot/no-response
1+
name: 'No Response'
22

3-
# Number of days of inactivity before an Issue is closed for lack of response
4-
daysUntilClose: 14
3+
# Both `issue_comment` and `scheduled` event types are required for this Action
4+
# to work properly.
5+
on:
6+
issue_comment:
7+
types: [created]
8+
schedule:
9+
# Schedule for five minutes after the hour, every hour
10+
- cron: '5 * * * *'
511

6-
# Label requiring a response
7-
responseRequiredLabel: "status: needs more info"
12+
# By specifying the access of one of the scopes, all of those that are not
13+
# specified are set to 'none'.
14+
permissions:
15+
issues: write
816

9-
# Comment to post when closing an Issue for lack of response. Set to `false` to disable
10-
closeComment: >
11-
This issue has been automatically closed because there has been no response
12-
to our request for more information from the original author. With only the
13-
information that is currently in the issue, we don't have enough information
14-
to take action. Please reach out if you have or find the answers we need so
15-
that we can investigate further.
17+
jobs:
18+
stale:
19+
runs-on: ubuntu-latest
20+
steps:
21+
- uses: actions/stale@v8
22+
with:
23+
any-of-labels: 'status: needs more info'
24+
close-issue-message: >
25+
Without additional information, we are unfortunately not able to resolve this issue.
26+
Therefore, we reluctantly closed this issue for now.
27+
If you run into this issue later, feel free to file a new issue with a reference to this issue.
28+
Add a description of detailed steps to reproduce, expected and current behaviour, logs and the output of 'flutter doctor -v'.
29+
Thanks for your contribution.
30+
days-before-close: 14

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /