-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider adding an "On Hold" label #10
Labels
improvement
This issue or pull request will add or improve functionality, maintainability, or ease of use
Comments
jsf9k
added
the
improvement
This issue or pull request will add or improve functionality, maintainability, or ease of use
label
Dec 18, 2020
This sounds good - I propose adding two labels:
Examples:
|
How about:
|
I'm on board with adding the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
improvement
This issue or pull request will add or improve functionality, maintainability, or ease of use
🚀 Feature Proposal
We should consider adding an "On Hold" label that is distinct from the "Blocked" label. See the discussion in cisagov/skeleton-generic#63. It may even make sense to create both an "On Hold" label and a more specific "Waiting for Kraken" label.
Motivation
When we are holding back a PR because we are waiting to gather enough PRs for a Kraken release, the PR is not "blocked" per se. There are also other cases where we might put a PR on hold even though it is not actually blocked by anything else, although perhaps the concept of a draft PR covers this case.
The advantage of creating a more specific "Waiting for Kraken" label is that we can easily do a search for it and thus identify all PRs that should be merged when it is time to release the Kraken.
The text was updated successfully, but these errors were encountered: