docs: add feature_request.yml issue template#257
Merged
Conversation
4 tasks
This file contains hidden or 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
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.
Summary
Adds a YAML form-based feature request template to decree, matching the structure and tone of the existing
bug_report.yml. Resolves the inconsistency where decree previously had only a bug template, causing feature asks to be filed as bugs or routed to Discussions.Fields (all match the acceptance criteria in the issue):
Auto-labels
enhancement.Closes #161
Notes
feature_request.yml, but those repos currently havefeature_request.md(legacy markdown form). This PR uses the richer YAML form to align with decree's existingbug_report.yml. Bringing the SDK repos in line is out of scope here..githubrepo) is left for a follow-up — flagship behavior is more discoverable when the template lives in the repo itself.Test plan
python3 -c 'import yaml; yaml.safe_load(...)')