Support self-hosted GitLab hosts in the extension manifest

[Copilot]

The extension only injected on gitlab.com, so self-hosted GitLab instances such as https://gitlab.qatools.com were excluded even though the runtime logic already works against same-origin GitLab pages.

• Manifest host matching

  • Replace the gitlab.com-only content script match with HTTPS patterns for the GitLab page types the extension already supports:
    • merge request diffs
    • commits
    • compares
  • Apply the same scoped patterns to web_accessible_resources
  • Drop the blanket host_permissions entry to avoid granting broader access than needed

• Documentation

  • Update README examples to use https://<gitlab-host>/... instead of hardcoding gitlab.com
  • Clarify that self-hosted GitLab instances are supported

• Result

  • The extension can now load on supported GitLab paths across arbitrary HTTPS-hosted GitLab deployments without changing the app runtime code

{
  "matches": [
    "https://*/*/-/merge_requests/*/diffs*",
    "https://*/*/-/commit/*",
    "https://*/*/-/compare/*"
  ]
}

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• gitlab.com
  • Triggering command: /home/REDACTED/work/_temp/ghcca-node/node/bin/node /home/REDACTED/work/_temp/ghcca-node/node/bin/node --enable-source-maps /home/REDACTED/work/_temp/copilot-developer-action-main/dist/index.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)