You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ jobs:
37
37
38
38
Then, you can answer an issue or PR and add the label from the config, in this case, `answered`.
39
39
40
-
After 10 days, if no one has added a new comment, the GitHub action will write:
40
+
After 10 days, if no one has added a new comment (or in the case of PRs, a new review or commit), the GitHub action will write:
41
41
42
42
```markdown
43
43
Assuming the original need was handled, this will be automatically closed now.
@@ -140,7 +140,7 @@ And finally, if:
140
140
141
141
* a PR has a label `needs-tests`
142
142
* the label was added _after_ the last comment
143
-
* the last comment was addded more than `691200` seconds (8 days) ago
143
+
* the last comment was added more than `691200` seconds (8 days) ago
144
144
145
145
...the GitHub action would close the PR with:
146
146
@@ -336,7 +336,7 @@ on:
336
336
* The `issues` option with a type of `label` will run it with each specific issue when you add a label.
337
337
* This way you can add a label to an issue that was answered long ago, and if the configured delay since the last comment is enough the GitHub action will close the issue right away.
338
338
* The `pull_request_target` option with a type of `label` will run it with each specific Pull Request made to your repo when you add a label.
339
-
* This way you can add a label to a PR that was answered long ago, or that was waiting for more comments from the author, etc. And if the configured delay since the last comment is enough the GitHub action will close the issue right away.
339
+
* This way you can add a label to a PR that was answered long ago, or that was waiting for more comments from the author, reviews, commits, etc. And if the configured delay since the last comment is enough the GitHub action will close the issue right away.
340
340
* The `workflow_dispatch` option allows you to run the action manually from the GitHub Actions tab for your repo.
0 commit comments