-
Notifications
You must be signed in to change notification settings - Fork 595
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
Broken links in bug template #5718
Comments
Issue was opened with an invalid reproduction link. Please make sure the repository is a valid, publicly-accessible github repository, and make sure the url is complete (example: https://github.com/googleapis/google-cloud-node) |
Please reopen this issue and give users a reasonable way to leave this kind of feedback. (I guess I could create a new issue with a fake reproduction link, but that doesn't seem like a very good use of my time.) |
Issue was opened with an invalid reproduction link. Please make sure the repository is a valid, publicly-accessible github repository, and make sure the url is complete (example: https://github.com/googleapis/google-cloud-node) |
Issue was opened with an invalid reproduction link. Please make sure the repository is a valid, publicly-accessible github repository, and make sure the url is complete (example: https://github.com/googleapis/google-cloud-node) |
Please make sure you have searched for information in the following guides.
A screenshot that you have tested with "Try this API".
n/a
Link to the code that reproduces this issue. A link to a public Github Repository or gist with a minimal reproduction.
n/a
A step-by-step description of how to reproduce the issue, based on the linked reproduction.
Create a bug report in this repo.
A clear and concise description of what the bug is, and what you expected to happen.
The Bug Report template for this repo contains links to the following URLs:
Both of these URLs redirect to https://cloud.google.com/nodejs/docs/reference/guides/latest/, which results in a 404. I expected both links to work.
A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **
Links shouldn't be broken.
The text was updated successfully, but these errors were encountered: