Back to feed

sledtools/pika branch #14

ssh-doc-merge-1774023052

docs: note git forge host

Target branch: master

Merge Commit: e9a5a39d2f814eab38d57d313b8c2cc1ee0cb4f1

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 #18 success

2 passed

head 23577242698f5d6cd5f2f236bd423ad8efff2841 · queued 2026-03-20 16:10:59 · 2 lane(s)

queued 7s · ran 2s

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

Summary

This branch adds a single documentation line to the manual QA checklist, explicitly noting the forge authentication and web review URL (https://git.pikachat.org/news). Previously, the 'Before Starting' section referenced only the canonical push remote over SSH but omitted the HTTPS web endpoint used for forge auth and code review. This closes a gap that could leave QA testers guessing which host to verify before running through the checklist.

Tutorial Steps

Add forge web host reference to the QA prerequisites

Intent: Make the manual QA checklist self-contained by documenting the HTTPS forge endpoint alongside the existing SSH push remote, so testers know exactly where forge authentication and web-based review live.

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

Evidence 
@@ -13,6 +13,7 @@ guessing which surfaces matter.
 ## Before Starting
 
 - Canonical push remote: `git@git.pikachat.org:pika.git`.
+- Forge auth and web review live on `https://git.pikachat.org/news`.
 - Confirm `/news/admin` loads and `Forge Health` shows `Poller`, `Generation Worker`, and `CI Runner` as `idle` or `active`, not `error`.

The Before Starting section of docs/forge-hosted-manual-qa.md already listed the SSH push remote but assumed the reader knew the web host for forge auth and review.

A new bullet is inserted at line 16, immediately after the SSH remote entry:

- Forge auth and web review live on `https://git.pikachat.org/news`.

This pairs the two access methods (SSH for pushes, HTTPS for the web UI) in one place so the remaining checklist items — such as confirming /news/admin health — have an unambiguous base URL to work from.

Diff