-
Notifications
You must be signed in to change notification settings - Fork 926
Create issue template with required fields #7275
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
Conversation
|
Size Report 1Affected Products
Test Logs |
Size Analysis Report 1Affected Products
Test Logs |
Just curious, is there a reason you made a separate file instead of modifying the existing one? |
Yes, I figured we would want to test/try it out in the repo before making it the official one. I added it to my nextjs testing repo https://github.com/dwyfrequency/next-platform-mvp-tests/blob/main/.github/ISSUE_TEMPLATE/bug_report.yaml so I am pretty confident but I thought it best to keep both for now until we finalize the V2 template. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for looking into this, a few comments and some questions and an AI for me I think (looking up how google-oss-bot works)
id: firebase-sdk-product | ||
attributes: | ||
label: Firebase SDK Product | ||
description: Describe your Firebase SDK Product |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Products,. People often are using multiple products. Maybe a dropdown or checkboxes would be good here, especially since the google-oss-bot auto-triages based on reading what's in this field. Actually we should try to find out what strings exactly the bot is looking for. I am not totally sure where the bot code lives, will try to look into it. If it's looking for "Firebase Product" which was in the old form, I guess we should leave the label the same. Also need to see what product strings it wants. If we stick with text input, let's put 2 packages in the placeholder example to show people they can do that.
multiple: true | ||
options: | ||
- Analytics | ||
- App-Check |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: AppCheck is how we usually do it in human-readable text settings
- type: dropdown | ||
id: firebase-sdk-products | ||
attributes: | ||
label: Firebase SDK Products |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Firebase SDK Product:
unless you are going to change the regex.
id: firebase-sdk-products | ||
attributes: | ||
label: Firebase SDK Products | ||
description: What Firebase SDK Products is your app using? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"are"? I think? That also sounds awkward. "Which Firebase Products are used in your app?"
Adding new issue template that specifies required fields