Skip to content

Add OpenWiki (org standard) - #2

Open
krishagel wants to merge 2 commits into
mainfrom
openwiki/add-caller
Open

krishagel wants to merge 2 commits into
mainfrom
openwiki/add-caller

Conversation

@krishagel

Copy link
Copy Markdown
Member

OpenWiki is now required on every PSD401 repo. This adds one file, .github/workflows/openwiki-update.yml, which calls the shared OpenWiki workflow in PSD401/.github.

What happens after you merge

  • The push to main builds this repo's wiki in openwiki/ from scratch. It uses Claude Haiku 5.5 on the district's Bedrock account and takes about 1–25 minutes depending on repo size.
  • The build opens a docs-only PR limited to openwiki/, which merges itself. AI review skips it.
  • After that, the wiki updates on every push to main and every Monday.

Owner: @krishagel. Please review and merge. Questions: psd401/psd-dev-standards, standards/06-cicd-enforcement.md.

OpenWiki is required on every PSD401 repo (decision 2026-10-07,
psd-dev-standards standards/00 and standards/06). This is a thin caller of
PSD401/.github reusable-openwiki.yml@main: it runs on push to main, Mondays
08:00 UTC, and on manual dispatch.

The first run builds openwiki/ from scratch (Claude Haiku 5.5 on Amazon
Bedrock, openwiki 0.3.3) and opens a docs-only PR limited to openwiki/,
which merges itself.
Copilot AI balanced review requested due to automatic review settings October 8, 2026 22:18

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

pull-requests: write
# @main is deliberate: org-owned reusable; central bumps must propagate
# (drift-kill design, psd-dev-standards standards/06). zizmor: ignore[unpinned-uses]
uses: PSD401/.github/.github/workflows/reusable-openwiki.yml@main # zizmor: ignore[unpinned-uses]
@claude

claude Bot commented Oct 8, 2026

Copy link
Copy Markdown

Review (PSD engineering standards)

Scope: single new file, .github/workflows/openwiki-update.yml (+25/-0). No Python source, tests, or pyproject.toml touched, so the pytest/ruff gates in CLAUDE.md don't apply here.

IMPORTANT

None.

Notes (not blocking)

  • uses: PSD401/.github/.../reusable-openwiki.yml@main + secrets: inherit + contents: write/pull-requests: write is a floating-ref call with broad trust — normally flagged as a supply-chain risk. Here it's explicitly intentional and documented inline (zizmor: ignore[unpinned-uses] + comment citing psd-dev-standards/06-cicd-enforcement.md's "drift-kill" design), and the PR body names an owner (@krishagel) and the standards doc to go to with questions. Since this is an org-mandated reusable workflow with the tradeoff called out and justified at the point of use, I'm not treating it as blocking — just confirming the justification is visible to reviewers, which it is.
  • Triggers/schedule match the PR description: push to main, weekly cron: "0 8 * * 1" (Monday 08:00 UTC), plus manual workflow_dispatch. concurrency: group: openwiki, cancel-in-progress: true correctly avoids redundant queued full-wiki rebuilds, with the "only the last run's output survives anyway" comment explaining why that's safe.
  • No secrets, student PII, or data handling introduced — this is CI/wiki-generation plumbing only.

CI weakening

None — no existing tests, workflows, or checks were removed or skipped.

NIT

None.

Verdict: Diff is clean. No changes requested.

…ry secret

The org OpenWiki workflow (PSD401/.github reusable-openwiki.yml) reads two
secrets: BEDROCK_API_KEY for the model and PSD_AUTOMATION_APP_PRIVATE_KEY
for the psd-automation App that opens and merges the docs PR. With
`secrets: inherit` the job also received every other org and repo secret.
This caller now passes those two by name.

Decision: Kris Hagel, 2026-10-09.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants