chore: update links in github issue templates (#513)

* chore: update links in github issue templates

* chore: update links in github issue templates

Source-Link: googleapis/synthtool@38fa49f
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:609822e3c09b7a1bd90b99655904609f162cc15acb4704f1edf778284c36f429

* Delete .github/ISSUE_TEMPLATE/bug_report.md

* Delete .github/ISSUE_TEMPLATE/feature_request.md

* Delete .github/ISSUE_TEMPLATE/question.md

---------

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
Co-authored-by: sofisl <[email protected]>

.github/.OwlBot.lock.yaml

@@ -13,5 +13,5 @@
 # limitations under the License.
 docker:
   image: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest
-  digest: sha256:a5af6af827a9fffba373151e1453b0498da288024cdd16477900dd42857a42e0
-# created: 2024-09-20T20:26:11.126243246Z
+  digest: sha256:609822e3c09b7a1bd90b99655904609f162cc15acb4704f1edf778284c36f429
+# created: 2024-10-01T19:34:30.797530443Z

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -24,12 +24,12 @@ body:
             e.js"
           required: true
         - label: "Check our Troubleshooting guide:
-            https://googlecloudplatform.github.io/google-cloud-node/#/docs/guid\
-            es/troubleshooting"
+            https://github.com/googleapis/google-cloud-node/blob/main/docs/trou\
+            bleshooting.md"
           required: true
         - label: "Check our FAQ:
-            https://googlecloudplatform.github.io/google-cloud-node/#/docs/guid\
-            es/faq"
+            https://github.com/googleapis/google-cloud-node/blob/main/docs/faq.\
+            md"
           required: true
         - label: "Check our libraries HOW-TO:
             https://github.com/googleapis/gax-nodejs/blob/main/client-libraries\
@@ -55,9 +55,9 @@ body:
         behavior you are experiencing. If the behavior is the same, it means
         that you are likely experiencing a bug with the API itself. In that
         case, please submit an issue to the API team, either by submitting an
-        issue in its issue tracker https://cloud.google.com/support/docs/issue-trackers, or by
+        issue in its issue tracker (https://cloud.google.com/support/docs/issue-trackers), or by
         submitting an issue in its linked tracker in the .repo-metadata.json
-        file https://b.corp.google.com/savedsearches/559654       
+        file https://b.corp.google.com/savedsearches/559654    
     validations:
       required: true
   - type: input

.github/ISSUE_TEMPLATE/processs_request.md

@@ -1,5 +1,4 @@
 ---
 name: Process Request
-about: Submit a process request to the library. Process requests are any requests related to library infrastructure, including CI/CD, publishing, releasing, etc. This issue template should primarily used by internal members.
-
----
+about: Submit a process request to the library. Process requests are any requests related to library infrastructure, for example CI/CD, publishing, releasing, broken links.
+---

.github/scripts/close-invalid-link.cjs

@@ -40,9 +40,12 @@ module.exports = async ({github, context}) => {
     const isBugTemplate = issue.data.body.includes('Link to the code that reproduces this issue');
 
     if (isBugTemplate) {
+        console.log(`Issue ${number} is a bug template`)
         try {
-            const link = issue.data.body.split('\n')[18].match(/(https?:\/\/g?i?s?t?\.?github.com\/.*)/);
+            const link = issue.data.body.split('\n')[18].match(/(https?:\/\/(gist\.)?github.com\/.*)/)[0];
+            console.log(`Issue ${number} contains this link: ${link}`)
             const isValidLink = (await fetch(link)).ok;
+            console.log(`Issue ${number} has a ${isValidLink ? 'valid' : 'invalid'} link`)
             if (!isValidLink) {
             await closeIssue(github, owner, repo, number);
             }