dark0707
/
px4-firmware
forked from Archive/PX4-Autopilot
1
0
Fork 0
Code Pull Requests Activity
px4-firmware/.github/stale.yml

16 lines
645 B
YAML
Raw Normal View History

Probot attempt to fix configuration (#11243)
2019-01-19 15:13:58 -04:00
# Number of days of inactivity before an issue becomes stale
daysUntilStale: 90
github: tone stalebot down My suggestion is to re-configure stale bot so it just adds the label stale but does not close the issue/PR. This enables us to look for outdated issues using the stale label and close them. This brings these advantages: - No more endless re-opening of PRs and issues which is not fun (and I will eventually give up on). - Less stalebot comment noise. (Because it is handy to look for all issues/PRs without any comments to see what is unanswered). - I'm not listed as "participating" in all the issues/PRs just because I was just fighting the stalebot. - Less notifications meaning we can see anything in the noise.
2019-10-01 05:05:24 -03:00
# Number of days of inactivity before a stale issue is closed, or `false` to disable
daysUntilClose: false
Probot attempt to fix configuration (#11243)
2019-01-19 15:13:58 -04:00
# Issues with these labels will never be considered stale
initial probot stale configuration (#9508)
2018-05-22 17:18:49 -03:00
exemptLabels:
Probot attempt to fix configuration (#11243)
2019-01-19 15:13:58 -04:00
- pinned
# Label to use when marking an issue as stale
github: tone stalebot down My suggestion is to re-configure stale bot so it just adds the label stale but does not close the issue/PR. This enables us to look for outdated issues using the stale label and close them. This brings these advantages: - No more endless re-opening of PRs and issues which is not fun (and I will eventually give up on). - Less stalebot comment noise. (Because it is handy to look for all issues/PRs without any comments to see what is unanswered). - I'm not listed as "participating" in all the issues/PRs just because I was just fighting the stalebot. - Less notifications meaning we can see anything in the noise.
2019-10-01 05:05:24 -03:00
staleLabel: stale
Probot attempt to fix configuration (#11243)
2019-01-19 15:13:58 -04:00
# Comment to post when marking an issue as stale. Set to `false` to disable
initial probot stale configuration (#9508)
2018-05-22 17:18:49 -03:00
markComment: >
This issue has been automatically marked as stale because it has not had
github: tone stalebot down My suggestion is to re-configure stale bot so it just adds the label stale but does not close the issue/PR. This enables us to look for outdated issues using the stale label and close them. This brings these advantages: - No more endless re-opening of PRs and issues which is not fun (and I will eventually give up on). - Less stalebot comment noise. (Because it is handy to look for all issues/PRs without any comments to see what is unanswered). - I'm not listed as "participating" in all the issues/PRs just because I was just fighting the stalebot. - Less notifications meaning we can see anything in the noise.
2019-10-01 05:05:24 -03:00
recent activity. Thank you for your contributions.
Probot attempt to fix configuration (#11243)
2019-01-19 15:13:58 -04:00
# Comment to post when closing a stale issue. Set to `false` to disable
github: tone stalebot down My suggestion is to re-configure stale bot so it just adds the label stale but does not close the issue/PR. This enables us to look for outdated issues using the stale label and close them. This brings these advantages: - No more endless re-opening of PRs and issues which is not fun (and I will eventually give up on). - Less stalebot comment noise. (Because it is handy to look for all issues/PRs without any comments to see what is unanswered). - I'm not listed as "participating" in all the issues/PRs just because I was just fighting the stalebot. - Less notifications meaning we can see anything in the noise.
2019-10-01 05:05:24 -03:00
closeComment: false