dashboard-checks: setup checks + template-update banner - #7
Merged
Conversation
Adds dashboard-checks.js, served from tools.opentechevents.org and loaded
by ote-template forks' docs/index.html (contract already wired there).
Self-contained vanilla JS, no build step; fails silently on any
network/CORS/parse error; idempotent.
Two features mounted into #ote-checks:
- Setup check (on demand, unauth GitHub API, cached per repo for the
session): Issues, ote-event label, Actions green, ote.config.json
placeholders, sample events. The "Actions can create PRs" permission
is shown as an unverifiable reminder — it needs administration:read
and can't be read unauthenticated.
- Template-update banner (on load): compares the fork's VERSION to the
latest ote-template release; shows the CHANGELOG slice and how to update.
deploy-tools.yml copies the file to the tools site root.
issue-to-pr.yml catches the PR-open 403 raised when "Allow GitHub Actions
to create and approve pull requests" is off and comments the fix on the
source issue — covering, at failure time, the one setup item the
client-side check cannot verify.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Client-side script served at
tools.opentechevents.org/dashboard-checks.js, loaded by ote-template forks'docs/index.html(contract already wired there — not changed). Self-contained vanilla JS, no build step, fails silently, idempotent.What lands
apps/dashboard-checks/dashboard-checks.js— the served artifact (+ tests for its pure helpers, README, eslint globals block).deploy-tools.yml— copies the file to the tools site root.issue-to-pr.yml— catches the PR-open 403 when Allow GitHub Actions to create and approve pull requests is off, and comments the fix on the source issue.Two features (mount
#ote-checks)ote-eventlabel, Actions running & green,ote.config.jsonplaceholders, sample events. The Actions can create PRs permission is shown as an unverifiable reminder (needsadministration:read), never a pass/fail — detected instead at PR-open time byissue-to-pr.yml.VERSIONvs latestote-templaterelease → version, CHANGELOG slice,git pull upstream main.Verification
pnpm lint/build/testgreen (11 new unit tests for semver, placeholder, sample-event, changelog-slice logic).Follow-up (not in this PR)
deploy-tools.ymlpublishes the script live.issue-to-pr.ymlchange reaches forks only when thev1tag moves to include it.🤖 Generated with Claude Code