Google Team Member
2380afd287
This change updates the feature request issue template to include required and recommended sections. New questions are added to gather more details on the problem, impact, willingness to contribute, and potential API/implementation ideas. Existing questions are rephrased for clarity PiperOrigin-RevId: 860199885
1.6 KiB
name, about, title, labels, assignees
| name | about | title | labels | assignees |
|---|---|---|---|---|
| Feature request | Suggest an idea for this project |
** Please make sure you read the contribution guide and file the issues in the right place. ** Contribution guide.
🔴 Required Information
Please ensure all items in this section are completed to allow for efficient triaging. Requests without complete information may be rejected / deprioritized. If an item is not applicable to you - please mark it as N/A
Is your feature request related to a specific problem?
Please describe the problem you are trying to solve. (Ex: "I'm always frustrated when I have to manually handle X...")
Describe the Solution You'd Like
A clear and concise description of the feature or API change you want. Be specific about input/outputs if this involves an API change.
Impact on your work
How does this feature impact your work and what are you trying to achieve? If this is critical for you, tell us if there is a timeline by when you need this feature.
Willingness to contribute
Are you interested in implementing this feature yourself or submitting a PR? (Yes/No)
🟡 Recommended Information
Describe Alternatives You've Considered
A clear and concise description of any alternative solutions or workarounds you've considered and why they didn't work for you.
Proposed API / Implementation
If you have ideas on how this should look in code, please share a pseudo-code example.
Additional Context
Add any other context or screenshots about the feature request here.