[docs] Update documentation for features from 2026-04-23#862
[docs] Update documentation for features from 2026-04-23#862danielmeppiel wants to merge 1 commit intomainfrom
Conversation
The [Unreleased] section was missing the Fixed entry documenting that clone and ls-remote error messages now surface host:port for self-hosted servers on non-default ports (e.g. Bitbucket Datacenter). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
danielmeppiel
added
automation
There was a problem hiding this comment.
Pull request overview
Adds the missing [Unreleased] changelog entry documenting the previously-merged fix that now surfaces host:port in generic-host clone / ls-remote error messages (PR #804, closes #798).
Changes:
- Add an
[Unreleased]### Fixedsection entry describing the generic-host custom port error-message improvement.
Show a summary per file
| File | Description |
|---|---|
| CHANGELOG.md | Adds the missing Unreleased “Fixed” entry for the generic-host host:port error-message fix (PR #804). |
Copilot's findings
- Files reviewed: 1/1 changed files
- Comments generated: 0
APM Review Panel VerdictDisposition: APPROVE PR: #862 -- Per-persona findings
CEO arbitrationThis is a clean, automated documentation maintenance PR. The sole change is a four-line CHANGELOG backfill for a bug fix that was confirmed merged (#804) but whose CHANGELOG entry was absent from the resulting commit. The entry format is correct (Keep a Changelog convention, PR reference, closes-issue link). All seven panel members have no blocking concerns. The pre-existing duplicate Required actions before mergeNone. Auto-merge is already enabled and is appropriate for this change. Optional follow-ups
|
…ict (#867) Merge Gate now waits for ALL 5 PR-time required checks (Build & Test (Linux) from ci.yml, plus Build/Smoke/Integration/Release-Validate (Linux) stubs from ci-integration-pr-stub.yml) and emits one verdict. This is the Tide / bors pattern: one gate to rule them all. Once this PR merges, branch protection can be flipped to require ONLY 'Merge Gate / gate'. The other 5 checks remain informational. This decouples the protection ruleset from CI workflow topology -- adding or renaming an underlying check no longer requires a ruleset edit. Script changes: - EXPECTED_CHECK (single string) -> EXPECTED_CHECKS (comma-separated). - Per-check state in parallel indexed arrays (works on bash 3.2+, no associative arrays required). - Fail-fast on the first failing check (exit 1 with annotation). - Timeout categorizes missing (never appeared) vs stuck (appeared but did not complete) and emits distinct error messages. - Same exit-code semantics as before, applied to the aggregate. Workflow changes: - Pass the 5 expected check names via EXPECTED_CHECKS env. - 'Merge Gate / gate' is excluded from the wait list by construction (it would deadlock waiting for itself). Tested live against PR #862 head SHA (all 5 OK -> exit 0) and against SHA 0000... (all 5 missing -> exit 2 with clear error annotation). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
This pull request was automatically closed because it expired on 2026-04-25T03:57:11.612Z.
|
Pull request was closed
Documentation Updates - 2026-04-23
This PR updates the documentation based on features merged in the last 24 hours.
Features Documented
host:portsurfacing in clone /ls-remoteerror messages (from fix(install): surface custom port in generic host clone/ls-remote error #804)Changes Made
### Fixedentry inCHANGELOG.mdunder[Unreleased]for the generic host port fixMerged PRs Referenced
fix(install): surface custom port in generic host clone/ls-remote error(closes [BUG] is_generic clone/ls-remote error path renders bare host, losing custom port for Bitbucket DC users #798)Notes
PR #804's commit message explicitly stated it added a CHANGELOG entry under
[Unreleased], but the entry was absent from the merged state. This PR adds the missing entry:No other documentation files required changes — the existing
docs/src/content/docs/guides/private-packages.mdalready documents custom port syntax for self-hosted servers, and this fix is an error-message quality improvement rather than a feature or API change.