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

The CI status link in README.md is broken #10426

Open
JoeWang1127 opened this issue Feb 22, 2024 · 1 comment
Open

The CI status link in README.md is broken #10426

JoeWang1127 opened this issue Feb 22, 2024 · 1 comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@JoeWang1127
Copy link
Contributor

The CI status in README.md is broken, for example: https://github.com/googleapis/google-cloud-java/blob/main/java-accessapproval/README.md#ci-status

image
@JoeWang1127 JoeWang1127 added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Feb 22, 2024
@lqiu96
Copy link
Contributor

lqiu96 commented May 20, 2024

I think this is probably something we copied over from the split repos. Does it make sense to even keep this for each module inside the monorepo? Perhaps we can just remove this section?

Going to downgrade this priority since it's not a customer issue.

@lqiu96 lqiu96 added priority: p3 Desirable enhancement or fix. May not be included in next release. and removed priority: p2 Moderately-important priority. Fix may not be included in next release. labels May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lqiu96 @JoeWang1127