Claudeandclaude[bot] b44bb82a3a fix(ci): build push and run links from GITHUB_SERVER_URL (#766) ...

night-red.mjs fell back to `https://github.com/<repo>/actions/runs/<id>` when
the API did not return html_url, and five publishing steps pushed to
`https://x-access-token:$TOKEN@github.com/<repo>`. On github.com nothing
breaks today; on any other server (GHES) the links and pushes would point to
the wrong host while GITHUB_API_URL is already honoured (#751).

- ci-proof.mjs: githubServerUrl(env) - GITHUB_SERVER_URL without a trailing
  slash, github.com when unset; night-red threads it as `server` into
  commentBody and nightRed, html_url from the API still wins.
- _beta-derived, _process (rebase and review document), _ship-review and
  release-review: `server="${GITHUB_SERVER_URL:-https://github.com}"` and
  push_url built from it; every token push uses "$push_url".

Tests: the night step executed on a non-standard server writes comment and
summary links to that host; every token push in every workflow takes its host
from GITHUB_SERVER_URL; the four publishing steps executed with
GITHUB_SERVER_URL=https://ghe.example.test push to that host, and to
github.com when it is empty. Checked: on the previous workflows and with the
hard-coded fallback restored in night-red these tests are red.

Issue: #766
User-Visible: no
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018qZfe7YS4rqEMKoVeS3GKd

2026-10-06 23:05:58 +00:00

..

ISSUE_TEMPLATE

docs v1.44.1: add the Telegram community chat (@ha_houseplan)

2026-07-27 12:51:48 +03:00

workflows

fix(ci): build push and run links from GITHUB_SERVER_URL (#766)

2026-10-06 23:05:58 +00:00