psa-systems/bunyip
Watch
9
0
Fork
You've already forked bunyip
 0
Code Issues Pull requests Projects Releases 18 Packages Wiki Activity Actions

docs(e2e): Forgejo Actions secrets + variables reference (BUNYIP-247) #269

Merged
nrupard merged 2 commits from docs/bunyip-247-forgejo-secrets-readme into main 2026-06-29 16:47:18 +02:00
Conversation 0 Commits 2 Files changed 2 +39 -1
nrupard commented 2026-06-29 16:19:02 +02:00
Owner
Copy link

What

Adds an authoritative reference for every repository-level Forgejo Actions secret and variable the workflows consume, in e2e/README.md, and links to it from the root README. Implements BUNYIP-247. Names and purpose only - no secret values.

Why

The knowledge was scattered: e2e/README.md explained the staging/production -> plain E2E_* mapping but listed no literal names; dev-docs/e2e.md enumerated the E2E names as a provisioning runbook only; the registry/release secret (PSA_SYSTEMS_PRIVATE_PACKAGE_PAT) was mentioned only in a workflow comment; and the two repo variables were undocumented. The root README had no link to the e2e suite docs at all.

Change

  • e2e/README.md: rename the Secret layout section to Forgejo Actions secrets and variables and add two tables:
    • Build/release: PSA_SYSTEMS_PRIVATE_PACKAGE_PAT (secret) plus PSA_SYSTEMS_PRIVATE_PACKAGE_OWNER and RUNS_ON_OPENSUSE_BASE_LATEST (variables), with kind, consuming workflow, and purpose.
    • E2E staging/production matrix mapped to the plain E2E_* names, with required/optional and the gated specs. Notes the deliberate absence of a production mail sink.
  • README.md: add a Contributing bullet linking to the reference.

Per the placement decision for BUNYIP-247, everything lives in e2e/README.md; the root README links to it.

Verification

Diffed the tables against the live .forgejo/workflows/*.yml: all 20 secrets + 2 variables present, no stale names. Docs-only change.

#BUNYIP-247

🤖 Generated with Claude Code

## What Adds an authoritative reference for every repository-level Forgejo Actions secret and variable the workflows consume, in `e2e/README.md`, and links to it from the root README. Implements BUNYIP-247. Names and purpose only - no secret values. ## Why The knowledge was scattered: `e2e/README.md` explained the staging/production -> plain `E2E_*` mapping but listed no literal names; `dev-docs/e2e.md` enumerated the E2E names as a provisioning runbook only; the registry/release secret (`PSA_SYSTEMS_PRIVATE_PACKAGE_PAT`) was mentioned only in a workflow comment; and the two repo variables were undocumented. The root README had no link to the e2e suite docs at all. ## Change - `e2e/README.md`: rename the `Secret layout` section to `Forgejo Actions secrets and variables` and add two tables: - Build/release: `PSA_SYSTEMS_PRIVATE_PACKAGE_PAT` (secret) plus `PSA_SYSTEMS_PRIVATE_PACKAGE_OWNER` and `RUNS_ON_OPENSUSE_BASE_LATEST` (variables), with kind, consuming workflow, and purpose. - E2E staging/production matrix mapped to the plain `E2E_*` names, with required/optional and the gated specs. Notes the deliberate absence of a production mail sink. - `README.md`: add a Contributing bullet linking to the reference. Per the placement decision for BUNYIP-247, everything lives in `e2e/README.md`; the root README links to it. ## Verification Diffed the tables against the live `.forgejo/workflows/*.yml`: all 20 secrets + 2 variables present, no stale names. Docs-only change. #BUNYIP-247 🤖 Generated with [Claude Code](https://claude.com/claude-code)
docs(e2e): authoritative Forgejo Actions secrets + variables reference
Some checks failed
E2E / Playwright against deployment (pull_request) Successful in 22s
Details
Check / fmt + clippy + build + tests (pull_request) Has been cancelled
Details
4de5c4b231 
Document every repository-level Forgejo Actions secret and variable the workflows consume, in e2e/README.md (names + purpose only, no values), and link to it from the root README. Closes the gap where the registry/release PAT and the two repo variables were undocumented and the E2E secret names lived only in the dev-docs provisioning runbook.

- e2e/README: rename the Secret layout section to "Forgejo Actions secrets and variables" and add two tables - build/release (PSA_SYSTEMS_PRIVATE_PACKAGE_PAT plus the two variables) and the E2E staging/production matrix mapped to the plain E2E_* names, marking the optional secrets and the deliberate absence of a production mail sink.
- README: add a Contributing bullet linking to the reference.

Verified the tables against the live .forgejo/workflows/*.yml: all 20 secrets + 2 variables present, no stale names.

#BUNYIP-247

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Merge branch 'main' into docs/bunyip-247-forgejo-secrets-readme
All checks were successful
E2E / Playwright against deployment (pull_request) Successful in 46s
Details
Check / fmt + clippy + build + tests (pull_request) Successful in 21m39s
Details
Create release / Create release from merged PR (pull_request) Has been skipped
Details
92ec6a1c52 
# Conflicts:
#	e2e/README.md
nrupard scheduled this pull request to auto merge when all checks succeed 2026-06-29 16:36:02 +02:00
nrupard deleted branch docs/bunyip-247-forgejo-secrets-readme 2026-06-29 16:47:18 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
psa-systems/bunyip!269
No description provided.