pulsar/.github/stale.yml

36 lines
1.5 KiB
YAML
Raw Normal View History

2017-05-09 20:10:24 +03:00
# Configuration for probot-stale - https://github.com/probot/stale
# Number of days of inactivity before an Issue or Pull Request becomes stale
daysUntilStale: 365
2017-05-09 20:10:24 +03:00
# Number of days of inactivity before a stale Issue or Pull Request is closed
daysUntilClose: 14
2017-05-09 20:10:24 +03:00
# Issues or Pull Requests with these labels will never be considered stale
exemptLabels:
- regression
2017-05-09 20:10:24 +03:00
- security
- triaged
# Label to use when marking as stale
staleLabel: stale
# Comment to post when marking as stale. Set to `false` to disable
markComment: >
2017-09-29 19:41:15 +03:00
Thanks for your contribution!
2017-05-09 20:10:24 +03:00
This issue has been automatically marked as stale because it has not had
2017-09-29 19:41:15 +03:00
recent activity. Because the Atom team treats their issues
2017-10-03 19:50:56 +03:00
[as their backlog](https://en.wikipedia.org/wiki/Scrum_(software_development)#Product_backlog), stale issues
are closed. If you would like this issue to remain open:
1. Verify that you can still reproduce the issue in the latest version of Atom
1. Comment that the issue is still reproducible and include:
* What version of Atom you reproduced the issue on
* What OS and version you reproduced the issue on
* What steps you followed to reproduce the issue
2017-09-29 19:41:15 +03:00
Issues that are labeled as triaged will not be automatically marked as stale.
2017-05-09 20:10:24 +03:00
# Comment to post when removing the stale label. Set to `false` to disable
unmarkComment: false
# Comment to post when closing a stale Issue or Pull Request. Set to `false` to disable
closeComment: false
# Limit to only `issues` or `pulls`
only: issues