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
Add support for the end-date option. This option
is similar to the start-date option except is allows
skipping items which were created after the end date.
In the Node.js project we want to mark PRs which
are older than 1 year old and have not been updated in
6 months as stale and then close them. The end-date
option is needed to be able to only operate on PRs
which are older than one year.
Signed-off-by: Michael Dawson <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -406,6 +406,14 @@ If set, the date must be formatted following the `ISO 8601` or `RFC 2822` standa
406
406
407
407
Default value: unset
408
408
409
+
#### end-date
410
+
411
+
The end date is used to ignore the issues and pull requests after the end date.
412
+
413
+
If set, the date must be formatted following the `ISO 8601` or `RFC 2822` standard.
414
+
415
+
Default value: unset
416
+
409
417
#### delete-branch
410
418
411
419
If set to `true`, the stale workflow will automatically delete the GitHub branches related to the pull requests automatically closed by the stale workflow.
test('processing an issue with no label and an end date as ISO 8601 being before the issue creation date will not make it stale nor close it when it is old enough and days-before-close is set to 0',async()=>{
test('processing an issue with no label and an end date as ISO 8601 being after the issue creation date will make it stale and close it when it is old enough and days-before-close is set to 0',async()=>{
test('processing an issue with no label and an end date as RFC 2822 being before the issue creation date will not make it stale nor close it when it is old enough and days-before-close is set to 0',async()=>{
test('processing an issue with no label and an end date as RFC 2822 being after the issue creation date will make it stale and close it when it is old enough and days-before-close is set to 0',async()=>{
test('processing an issue with no label will make it stale and close it, if it is old enough only if days-before-close is set to > 0 and days-before-issue-close is set to 0',async()=>{
Copy file name to clipboardExpand all lines: action.yml
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -144,6 +144,10 @@ inputs:
144
144
description: 'The date used to skip the stale action on issue/pull request created before it (ISO 8601 or RFC 2822).'
145
145
default: ''
146
146
required: false
147
+
end-date:
148
+
description: 'The date used to skip the stale action on issue/pull request created after it (ISO 8601 or RFC 2822).'
149
+
default: ''
150
+
required: false
147
151
exempt-assignees:
148
152
description: 'The assignees which exempt an issue or a pull request from being marked as stale. Separate multiple assignees with commas (eg. "user1,user2").'
0 commit comments