acf4816994
While the idea of cleaning up the the PRs list by nudging reviewers with the stale message and closing PRs that didn't got a review in time cloud work for the maintainers, in practice it discourages contributors to submit contributions. Keeping PRs open and not providing feedback also doesn't help with contributors motivation, so while I'm disabling this feature of the bot we still need to come up with a process that will help us to keep the number of PRs in check, but celebrate the work contributors already did instead of ignoring it, or dismissing in the form of a "stale" alerts, and automatically closing PRs.
31 lines
1.1 KiB
YAML
31 lines
1.1 KiB
YAML
# Number of days of inactivity before an issue becomes stale
|
|
daysUntilStale: 90
|
|
# Number of days of inactivity before a stale issue is closed
|
|
daysUntilClose: 7
|
|
# Issues with these labels will never be considered stale
|
|
exemptLabels:
|
|
- pinned
|
|
- security
|
|
- With reproduction steps
|
|
- attached PR
|
|
- regression
|
|
- release blocker
|
|
# Issues on a milestone will never be considered stale
|
|
exemptMilestones: true
|
|
# Label to use when marking an issue as stale
|
|
staleLabel: stale
|
|
# Comment to post when marking an issue as stale. Set to `false` to disable
|
|
markComment: >
|
|
This issue has been automatically marked as stale because it has not been commented on for at least three months.
|
|
|
|
The resources of the Rails team are limited, and so we are asking for your help.
|
|
|
|
If you can still reproduce this error on the `7-0-stable` branch or on `main`,
|
|
please reply with all of the information you have about it in order to keep the issue open.
|
|
|
|
Thank you for all your contributions.
|
|
# Comment to post when closing a stale issue. Set to `false` to disable
|
|
closeComment: false
|
|
# Limit to only `issues` or `pulls`
|
|
only: issues
|