Skip to content

add API issue tracker table to README #14024 #14032

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
Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

add API issue tracker table to README #14024 #14032

wants to merge 2 commits into from

Conversation

Aarshpatel12
Copy link

This PR addresses [issue #14024]

🔧 Changes Made:

Added a new section in README.rst titled API Issue Tracker Directory

Populated the table with direct links to public Google Issue Tracker pages for common APIs:

BigQuery

Cloud Storage

Pub/Sub

Translation API

Vision API

✅ Purpose:
To help developers quickly navigate to the corresponding issue trackers for APIs when encountering bugs or requesting features.

📌 Note:
This PR only updates the documentation and does not include any breaking changes or code modifications.

@Aarshpatel12 Aarshpatel12 requested a review from a team as a code owner June 24, 2025 04:45
@snippet-bot Snippet Bot
Copy link

snippet-bot bot commented Jun 24, 2025

Here is the summary of changes.

You are about to delete 8 region tags.

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

  • Refresh this comment

@parthea
Copy link
Contributor

parthea commented Jun 30, 2025

Hi @Aarshpatel12,

This PR mentions updating README but there are 500+ files changed. My initial thought is that rather than add a new API Issue Tracker Directory section, the existing portion of the README under Libraries should include the relevant issue tracker information. Some entries are missing today, and that could be due to a either bug in the updateapilist.py script or missing information in the package specific .repo-metadata.json which is the source of truth for the issue tracker link. If you're still interested in working on this, please feel free to comment on the existing issue if you have specific questions

@parthea parthea marked this pull request as draft June 30, 2025 13:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@Aarshpatel12 @parthea