Back to feed

ssh-doc-merge-1774023052

sledtools/pika · branch #14 · target master · updated 2026-03-20 16:11:29

branch: merged tutorial: ready ci: success

CI

Run #18 · success · 2 lane(s)

head 23577242698f5d6cd5f2f236bd423ad8efff2841 · queued 2026-03-20 16:10:59

started 2026-03-20 16:11:06

finished 2026-03-20 16:11:08

Lane #48 · check-pika-rust · success · ./scripts/pikaci-staged-linux-remote.sh run pre-merge-pika-rust

lane id pika_rust · retries 0 · queued 2026-03-20 16:10:59

pikaci run 20260320T161108Z-d2f8d88b · target pre-merge-pika-rust

started 2026-03-20 16:11:06

finished 2026-03-20 16:11:08

[pikaci] run started: 20260320T161108Z-d2f8d88b · pre-merge-pika-rust · Run the VM-backed Rust tests from the pre-merge pika lane
[pikaci] run finished: 20260320T161108Z-d2f8d88b · status=skipped · skipped; no changed files matched 13 filter(s)
error (ignored): SQLite database '/var/lib/pika-news/.cache/nix/eval-cache-v6/1dd8a6309db8adc249a319b4e2e9f1888027d872972b317d7f1c7c5c9899839a.sqlite' is busy
[pikaci-tools] staged-linux-remote: resolution=nix-build package_root=/nix/store/cn1phn2zmwwmja4dbc5n1n8ny18pa4vn-pikaci-0.1.0
[pikaci-tools] staged-linux-remote: pikaci=/nix/store/cn1phn2zmwwmja4dbc5n1n8ny18pa4vn-pikaci-0.1.0/bin/pikaci
[pikaci-tools] staged-linux-remote: helper=/nix/store/cn1phn2zmwwmja4dbc5n1n8ny18pa4vn-pikaci-0.1.0/bin/pikaci-fulfill-prepared-output
[pikaci-tools] staged-linux-remote: launcher=/nix/store/cn1phn2zmwwmja4dbc5n1n8ny18pa4vn-pikaci-0.1.0/bin/pikaci-launch-fulfill-prepared-output
Lane #49 · check-pika-followup · success · ./scripts/pikaci-staged-linux-remote.sh run pre-merge-pika-followup

lane id pika_followup · retries 0 · queued 2026-03-20 16:10:59

pikaci run 20260320T161108Z-0ab773a3 · target pre-merge-pika-followup

started 2026-03-20 16:11:06

finished 2026-03-20 16:11:08

[pikaci] run started: 20260320T161108Z-0ab773a3 · pre-merge-pika-followup · Run the VM-backed non-Rust follow-up checks from the pre-merge pika lane
[pikaci] run finished: 20260320T161108Z-0ab773a3 · status=skipped · skipped; no changed files matched 23 filter(s)
[pikaci-tools] staged-linux-remote: resolution=nix-build package_root=/nix/store/cn1phn2zmwwmja4dbc5n1n8ny18pa4vn-pikaci-0.1.0
[pikaci-tools] staged-linux-remote: pikaci=/nix/store/cn1phn2zmwwmja4dbc5n1n8ny18pa4vn-pikaci-0.1.0/bin/pikaci
[pikaci-tools] staged-linux-remote: helper=/nix/store/cn1phn2zmwwmja4dbc5n1n8ny18pa4vn-pikaci-0.1.0/bin/pikaci-fulfill-prepared-output
[pikaci-tools] staged-linux-remote: launcher=/nix/store/cn1phn2zmwwmja4dbc5n1n8ny18pa4vn-pikaci-0.1.0/bin/pikaci-launch-fulfill-prepared-output

merge commit e9a5a39d2f814eab38d57d313b8c2cc1ee0cb4f1

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