Remove fake tasks #19
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Peechiz
requested review from
chmurph2 and
invacuo
and removed request for
a team
paulslaby
approved these changes
Mar 12, 2024
|
❤️🔥 YES! |
done |
|
Just throwing out an alternate: What if the instruction were to review the list and remove any that were not risks and only keep risks that apply to your change? |
Peechiz
commented
Mar 12, 2024
avinash-vllbh
approved these changes
Mar 12, 2024
|
Reminder this is a PUBLIC repo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stakeholder Overview (learn more)
Unchecked risk categories are not unfinished "tasks", but github parses them as such. This also conflicts with PRs that wish to use the task feature to keep track of features within a PR. This would change the format to a list and encourage people to use appropriate emoji instead for readability.
Risk Estimate (learn more)
This is an example of what usage might look like, and also an accurate risk estimate of the PR. (risk is super low, but it does affect every repo.)