rules_kotlin
rules_kotlin copied to clipboard
Add configuration for stale bot
Should help with issue/PR triage.
Ideally we would have the resources to address and resolve all issues, and review and merge all pull requests. But we don't. Rather than leave these open indefinitely, it's better to set user expectations that these will just age out.
This is the same config used in rules_nodejs, rules_docker, and rules_python.
Note: I think someone with permissions needs to create the "Can Close?" label on this repo before the GH action runs
Note: I think someone with permissions needs to create the "Can Close?" label on this repo before the GH action runs
Assuming we take this PR (and I'm inclined to, once we figure out the other issues with specific labels) I"ll add it.
Gotcha. I'll take care of it.
On Fri, Jul 9, 2021, 20:01 Alex Eagle @.***> wrote:
@.**** commented on this pull request.
In .github/workflows/stale.yml https://github.com/bazelbuild/rules_kotlin/pull/551#discussion_r667280147 :
with:
repo-token: ${{ secrets.GITHUB_TOKEN }}# NB: We start with very long duration while trimming existing issues,# with the hope to reduce when/if we get better at keeping up with user support.# The number of days old an issue can be before marking it stale.days-before-stale: 180# Number of days of inactivity before a stale issue is closeddays-before-close: 30# If an issue/PR is assigned, trust the assignee to stay involved# Can revisit if these get staleexempt-all-assignees: true# Issues with these labels will never be considered staleexempt-issue-labels: "need: discussion,cleanup"I assume they are exact, we could check the specification. I'm on vacation at the moment, feel free to amend or add commits.
— You are receiving this because your review was requested. Reply to this email directly, view it on GitHub https://github.com/bazelbuild/rules_kotlin/pull/551#discussion_r667280147, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACQ3YS25XOSNKR4XVVITHDTW6ZZFANCNFSM46JCLUJQ .