Update issue templates to match the current resource cards

The "Open an Issue" templates hadn't caught up with fields the resource
detail cards gained in the last couple of redesigns.

- resource-software.yml: added the "Data Warehouse & Analytics"
  subcategory (added to the catalog after this template was written).
- resource-software.yml / resource-saas.yml / resource-services.yml:
  added an optional Repository field — these three sections all
  support a `github` front-matter field (owner/repo or full URL) that
  adds a "View on GitHub" button and a Repository row to the detail
  page, but there was previously no way to supply it via an issue.
- resource-events.yml: added End date, Online link, Registration link,
  and Recording link — all optional, matching date_end/online_url/
  registration_url/recording_url on the Events detail card. Recording
  link is noted as only applicable once a recording actually exists,
  same guidance as elsewhere.

Training, Books, and Community templates already matched their current
cards — no changes needed there.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Author: Mazizova

.github/ISSUE_TEMPLATE/resource-events.yml

@@ -29,6 +29,12 @@ body:
     attributes:
       label: "Date"
       placeholder: "e.g. 2027-06-15"
+  - type: input
+    id: date_end
+    attributes:
+      label: "End date (optional)"
+      description: "Only for a multi-day event."
+      placeholder: "e.g. 2027-06-17"
   - type: dropdown
     id: format
     attributes:
@@ -41,7 +47,25 @@ body:
     id: location
     attributes:
       label: "City, Country"
+      description: "Leave blank for an online-only event."
       placeholder: "e.g. Amsterdam, Netherlands"
+  - type: input
+    id: online_url
+    attributes:
+      label: "Online link (optional)"
+      description: "Livestream or virtual-attendance URL, for an online or hybrid event."
+      placeholder: "https://..."
+  - type: input
+    id: registration_url
+    attributes:
+      label: "Registration link (optional)"
+      placeholder: "https://..."
+  - type: input
+    id: recording_url
+    attributes:
+      label: "Recording link (optional)"
+      description: "Only once a recording actually exists — typically for a past event."
+      placeholder: "https://..."
   - type: dropdown
     id: subcategory
     attributes:

.github/ISSUE_TEMPLATE/resource-saas.yml

@@ -17,6 +17,12 @@ body:
       placeholder: "https://..."
     validations:
       required: true
+  - type: input
+    id: github
+    attributes:
+      label: "Repository (optional)"
+      description: "Only if there's a public GitHub repo separate from the URL above."
+      placeholder: "https://github.com/owner/repo"
   - type: textarea
     id: description
     attributes:

.github/ISSUE_TEMPLATE/resource-services.yml

@@ -17,6 +17,12 @@ body:
       placeholder: "https://..."
     validations:
       required: true
+  - type: input
+    id: github
+    attributes:
+      label: "Repository (optional)"
+      description: "Only if there's a public GitHub repo separate from the URL above."
+      placeholder: "https://github.com/owner/repo"
   - type: textarea
     id: description
     attributes:

.github/ISSUE_TEMPLATE/resource-software.yml

@@ -17,6 +17,12 @@ body:
       placeholder: "https://..."
     validations:
       required: true
+  - type: input
+    id: github
+    attributes:
+      label: "Repository (optional)"
+      description: "Only if there's a public GitHub repo separate from the URL above."
+      placeholder: "https://github.com/owner/repo"
   - type: textarea
     id: description
     attributes:
@@ -33,6 +39,7 @@ body:
         - Database Software
         - Monitoring & Observability
         - Backup & Recovery
+        - Data Warehouse & Analytics
         - Replication & High Availability
         - Proxies & Traffic Management
         - Connectors & Drivers