Skip to content

Conversation

@alexeagle
Copy link
Contributor

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.

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.
@alexeagle
Copy link
Contributor Author

Note: I think someone with permissions needs to create the "Can Close?" label on this repo before the GH action runs

Copy link
Collaborator

@cgruber cgruber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love it in general, one quick question before merging.

# Can revisit if these get stale
exempt-all-assignees: true
# Issues with these labels will never be considered stale
exempt-issue-labels: "need: discussion,cleanup"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these exact, or are they a match? We have labels more like this: type: cleanup I don't think these exempt labels would ever trigger on this project.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume they are exact, we could check the specification. I'm on vacation at the moment, feel free to amend or add commits.

@cgruber cgruber added component: common P1 status: in review Solution being reviewed type: cleanup Refactorings, idiomatic transforms, tech debt payoff labels Jul 9, 2021
@cgruber cgruber added this to the Candidate 1.5 milestone Jul 9, 2021
@cgruber
Copy link
Collaborator

cgruber commented Jul 10, 2021

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.

@cgruber
Copy link
Collaborator

cgruber commented Jul 10, 2021 via email

@cgruber cgruber removed this from the Candidate 1.5 milestone Sep 3, 2021
@cgruber cgruber self-assigned this Oct 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component: common P1 status: in review Solution being reviewed type: cleanup Refactorings, idiomatic transforms, tech debt payoff

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants