Back to feed

sledtools/pika branch #13

ssh-doc-merge-1774022391

docs: note canonical forge remote

Target branch: master

Merge Commit: b192ef216384b34ce06b6acdc30856ed8d2396de

branch: merged tutorial: ready ci: success
Open CI Details

Continuous Integration

CI: success

Compact status on the review page, with full logs on the CI page.

Open CI Details

Latest run #17 success

2 passed

head 02586b89501acc937f5200d4a29d853cd54ea880 · queued 2026-03-20 16:00:41 · 2 lane(s)

queued 2m 26s · ran 3s

check-pika-rust · success check-pika-followup · success

Summary

This branch adds a single documentation line to the forge-hosted manual QA checklist, recording the canonical push remote (git@git.pikachat.org:pika.git) in the "Before Starting" section. The change ensures that anyone running through the QA procedure knows exactly which SSH remote to target, preventing accidental pushes to a mirror or secondary remote.

Tutorial Steps

Add canonical push remote to the QA prerequisites

Intent: Document the authoritative SSH push remote so QA operators do not have to guess or look it up elsewhere. Placing it as the first bullet in the 'Before Starting' section makes it the very first thing a tester sees before running any checks.

Affected files: docs/forge-hosted-manual-qa.md

Evidence 
@@ -12,6 +12,7 @@ guessing which surfaces matter.
 
 ## Before Starting
 
+- Canonical push remote: `git@git.pikachat.org:pika.git`.

A new bullet point is inserted at the top of the Before Starting checklist in docs/forge-hosted-manual-qa.md:

- Canonical push remote: `git@git.pikachat.org:pika.git`.

This sits directly above the existing health-check and mirror-mode bullets, establishing the correct remote URL as prerequisite knowledge before any QA steps are executed. The SSH-style URL (git@git.pikachat.org:pika.git) makes it clear that this is the forge's own host, not a GitHub/GitLab mirror, which is especially important in setups where multiple remotes are configured.

Diff