repo: add Tracking Issue issue template
#182
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
hinto-janai
commented
Jun 20, 2024
| A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. | ||
| Instead, open a dedicated issue for the specific matter. | ||
|
|
||
| ### What |
There was a problem hiding this comment.
These are ### instead of ## like other issue templates because:
rust-lang/rustdoes it like this- It makes this template stand-out
|
Btw I plan on retroactively making one of these for |
|
Active example: #183 |
Boog900
approved these changes
Jun 20, 2024
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.
This adds
.github/ISSUE_TEMPLATE/tracking_issue.mdand fixes some formatting in other templates.The purpose of this is to track wider efforts that may contain multiple PRs and/or are generally spread out. These don't usually contain the why, but if they do, they are brief. These contain no implementation detail or the how, as those are for the issues/PRs that are being tracked.
For example:
unsafe_op_in_unsafe_fnwarn-by-default rust-lang/rust#123916A big difference between this and a proposal is that tracking issues already have consensus, i.e. the thing in question is already decided on. The what/why/where is already answered, all that is left is implementation.