Skip to content

Commit

Permalink
fix: update node issue template (#582)
Browse files Browse the repository at this point in the history
  • Loading branch information
stephenplusplus authored Jun 17, 2020
1 parent c4f3059 commit b10590a
Showing 1 changed file with 8 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -8,13 +8,18 @@ Thanks for stopping by to let us know something could be better!

**PLEASE READ**: If you have a support contract with Google, please create an issue in the [support console](https://cloud.google.com/support/) instead of filing on GitHub. This will ensure a timely response.

Please run down the following list and make sure you've tried the usual "quick fixes":
1) Is this a client library issue or a product issue?
This is the client library for {{metadata['name_pretty']}}. We will only be able to assist with issues that pertain to the behaviors of this library. If the issue you're experiencing is due to the behavior of the product itself, please visit the [{{metadata['name_pretty']}} Support page]({{metadata['support_documentation']}}) to reach the most relevant engineers.

2) Did someone already solve this?
- Search the issues already opened: https://github.com/{{metadata['repository']}}/issues
- Search the issues on our "catch-all" repository: https://github.com/googleapis/google-cloud-node
- Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js
- Search or ask on StackOverflow (engineers monitor these tags): http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js

If you are still having issues, please be sure to include as much information as possible:
3) Do you have a support contract?
Please create an issue in the [support console](https://cloud.google.com/support/) to ensure a timely response.

If the support paths suggested above still do not result in a resolution, please provide the following details.

#### Environment details

Expand Down

0 comments on commit b10590a

Please sign in to comment.