googleapis / googleapis/librarian
config: find suitable issue trackers for all APIs
Open
Nobody has claimed this yet.
priority: p3
- Dominant language
- Go
- Stars
- 45
- Forks
- 62
- Avg merge
- 18h 32m
- Merged PRs (30d)
- 175
Description
Some new_issue_uri values in sdk.yaml are incorrect (e.g. they're for the Python repo).
Assuming we think there's value in having issue tracker URIs (which I personally think there is), we should audit which APIs we don't currently have *good* values for, and try to find appropriate ones.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the new_issue_uri entries in sdk.yaml and comparing them with the corresponding APIs' issue trackers. Done means auditing all APIs and correcting missing or unsuitable URIs so each value points to an appropriate tracker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- api, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100