[go: nahoru, domu]
Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update the Client Libraries Issues link(s) in the README to point to template for filing an issue #12723

Open
ohmayr opened this issue May 22, 2024 · 1 comment
Open

Update the Client Libraries Issues link(s) in the README to point to template for filing an issue #12723

ohmayr opened this issue May 22, 2024 · 1 comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: process A process-related concern. May include testing, release, or the like.

Comments

@ohmayr
Copy link
Contributor
ohmayr commented May 22, 2024

For projects where we are creating issues directly in google-cloud-python we could update this link to point to template for filing an issue: For example, https://github.com/googleapis/google-cloud-python/issues/new?assignees=&labels=&projects=&template=bug_report.md

One benefit of this is that we can set the labels parameter in the url which is empty by default.

For example, we could add the type: bug label and api: access approval label , using url encoding for the colon and space characters.
https://github.com/googleapis/google-cloud-python/issues/new?assignees=&labels=type%3A%20bug%2Capi%3A%20accessapproval&projects=&template=bug_report.md

As long as the priority remains unset, the bug will be considered un-triaged and will still appear in the un-triaged list.
@ohmayr ohmayr added priority: p2 Moderately-important priority. Fix may not be included in next release. type: process A process-related concern. May include testing, release, or the like. labels May 22, 2024
@ohmayr ohmayr mentioned this issue May 22, 2024
Merged
@vchudnov-g
Copy link
Contributor

The links to the new issue templates (#12710) explicitly include the labels I configured in the URL. So for bugs, we can use that URL (which already includes the bug label) and just add the api: XXX label. Note that the proposed bug template will also ask users to fill in the API name, which will be useful ifthey get there not via the README.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: process A process-related concern. May include testing, release, or the like.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vchudnov-g @ohmayr