Back to feed

sledtools/pika branch #1

qa/forge-smoke-20260319-1

qa: confirm post-receive hook

Target branch: master

Merge Commit: 5a79746061faf9aded05380dc2941f77d03cbe3c

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

Continuous Integration

CI: failed

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

Open CI Details

Latest run #3 failed

1 failed

head 0db933972a4cccd84791ad3870977ce74a567d85 · queued 2026-03-19 19:44:51 · 1 lane(s)

queued 19s · ran 54s

check-pika · failed

Summary

Branch qa/forge-smoke-20260319-1 adds timestamped smoke-test markers to the forge-hosted manual QA runbook. Three append-only log lines were introduced to docs/forge-hosted-manual-qa.md, confirming that the post-receive hook fires correctly on branch creation and subsequent force-pushes. No functional code is changed; the branch exists purely as a QA probe to validate the hosted forge's Git hook pipeline.

Tutorial Steps

Append initial smoke-test creation marker

Intent: Record that the hosted forge smoke branch was created, proving the post-receive hook triggers on the initial push of a new branch.

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

Evidence 
@@ -83,3 +83,9 @@
+
+Hosted forge smoke branch created at 2026-03-19T19:00Z.

A blank line and a timestamped creation marker were appended after the existing nightly-page QA checklist (line 85 onward). This line serves as the baseline event: when the branch first appears on the forge, the post-receive hook should process this commit and the marker provides a human-readable proof point.

The timestamp format (2026-03-19T19:00Z) is ISO-8601 in UTC, making it straightforward to correlate with server-side hook logs.

Append first update marker via force-push

Intent: Verify that the post-receive hook fires again when an existing branch is force-pushed with new content.

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

Evidence 
@@ -83,3 +83,9 @@
+Hosted forge smoke branch updated at 2026-03-19T19:45Z.

A second timestamped line was added 45 minutes after the branch creation marker. Because the branch already existed, this commit would have arrived as a force-push (or fast-forward). The post-receive hook must detect the ref update and re-process the branch.

During QA, compare this timestamp against the hook's execution log to confirm latency and correctness.

Append second update marker to confirm repeated hook idempotency

Intent: Ensure the post-receive hook remains stable across multiple consecutive updates to the same branch within a short window.

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

Evidence 
@@ -83,3 +83,9 @@
+Hosted forge smoke branch updated at 2026-03-19T19:50Z.

A third line was appended only 5 minutes after the previous update. This rapid-fire push tests that the hook does not debounce, drop, or duplicate events when the same ref is updated in quick succession.

QA checklist derived from this branch

  1. Confirm the forge received all three commits (creation + two updates).
  2. Verify the post-receive hook fired exactly three times by inspecting server logs.
  3. Ensure each hook invocation processed the correct old-sha → new-sha transition.
  4. Confirm no duplicate or missing webhook deliveries downstream.

Diff