Skip to content

Commit

Permalink
chore(github): update comments stale period
Browse files Browse the repository at this point in the history
  • Loading branch information
samcx committed Dec 24, 2024
1 parent 7a47ed5 commit c59a43b
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion .github/comments/invalid-reproduction.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Ensure the link is pointing to a codebase that is accessible (e.g. not a private

### What happens if I don't provide a sufficient minimal reproduction?

Issues with the `please add a complete reproduction` label that receives no meaningful activity (e.g. new comments with a reproduction link) are automatically closed and locked after 30 days.
Issues with the `please add a complete reproduction` label that receives no meaningful activity (e.g. new comments with a reproduction link) are automatically closed and locked after **2** days.

If your issue has _not_ been resolved in that time and it has been closed/locked, please open a new issue with the required reproduction.

Expand Down
2 changes: 1 addition & 1 deletion .github/comments/simplify-reproduction.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ If you cannot create a clean reproduction, another way you can help the maintain

### What happens if I don't provide a sufficient minimal reproduction?

Issues with the `please simplify reproduction` label that receive no meaningful activity (e.g. new comments with a simplified reproduction link) are automatically closed and locked after 30 days.
Issues with the `please simplify reproduction` label that receive no meaningful activity (e.g. new comments with a simplified reproduction link) are automatically closed and locked after **14** days.

If your issue has _not_ been resolved in that time and it has been closed/locked, please open a new issue with the required reproduction.

Expand Down
2 changes: 1 addition & 1 deletion .github/comments/verify-canary.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ Next.js does not backport bug fixes to older versions of Next.js. Instead, we ar

### What happens if I don't verify against the canary version of Next.js?

An issue with the `please verify canary` that receives no meaningful activity (e.g. new comments that acknowledge verification against `canary`) will be automatically closed and locked after 30 days.
An issue with the `please verify canary` that receives no meaningful activity (e.g. new comments that acknowledge verification against `canary`) will be automatically closed and locked after **14** days.

If your issue has not been resolved in that time and it has been closed/locked, please open a new issue, with the required reproduction, using `next@canary`.

Expand Down

0 comments on commit c59a43b

Please sign in to comment.