Repository navigation
chore: retire the settings publisher, sync and audit - #106
Conversation
The owner retired the token-driven settings automation on 2026-11-14. There is no standing organization-owner credential any more, and the rules now live in organization rulesets aimed at all repositories. Remove bin/, lib/, tests/, community-health/, the release scripts, the publish, publish-planning, sync-project, check-project-health, audit and semantic-release workflows, and every config file that only those tools read. Keep config/planning.json unchanged: three agent skills read its Project Status names. Keep the required "Policy validation" job as a small real check: every tracked JSON file parses, relative Markdown links resolve, and every workflow action is pinned to a full commit SHA. Rewrite README.md, AGENTS.md and CONTRIBUTING.md to describe the repository as it is now. Co-Authored-By: Claude <noreply@anthropic.com>
Dependency Review✅ No vulnerabilities or license issues found.Scanned Files
|
Co-Authored-By: Claude <noreply@anthropic.com>
A PR body or title edit right after a push started a second run that cancelled the in-progress run for the same head (cancel-in-progress), leaving a cancelled Dependency review check on the commit. Co-Authored-By: Claude <noreply@anthropic.com>
Self-reviewReviewed by fresh-context independent reviewer subagents, each given the intent brief:
The current head Findings
|
The repository's CodeQL default setup no longer analyses JavaScript, which this pull request removes. This empty commit gives the pull request a head without the stale failed JavaScript analysis. Co-Authored-By: Claude <noreply@anthropic.com>
|
Reviewed head This head adds one empty commit on top of Why the commit exists: the only failing check on the previous head was CodeQL "Analyze (javascript-typescript)". This pull request removes the repository's only JavaScript, so that analysis had nothing to analyse. With the owner's approval of the retirement, the repository's CodeQL default-setup languages were set to No findings; no content changed since the last reviewed head. |
Summary
Retires the settings automation in this repository, so nobody, human or
agent, can run the old publisher, Project sync or drift audit from it any more.
The repository stays (it is not archived) and now says plainly what it is: the
home of Atrinik's settings record, holding
config/planning.jsonand a smallCI check today. A later pull request adds the read-only settings check and
Atrinik's baseline file.
The owner decided this on 2026-11-14. The tooling needed a standing
organization-owner credential, which is gone, and its rules now live in
organization rulesets that target all repositories.
Intent brief
this repository, and replace the long desired-state documentation with a
short, accurate description of what the repository is now.
bin/,lib/,tests/,community-health/, the release scriptsand every config file that only those tools read. With no code left there
is nothing to run, and the history is kept in Git and in release
v2.26.0(the current
maincommit).config/planning.jsonbyte for byte. Threeatrinik-developmentagent skills read its Project Status names.
03 - Required CI - github-settingsrequiresPolicy validationandConventional PR title.Policy validationbecomes a small real check: every tracked JSON fileparses, every relative Markdown link points at a tracked path, and every
workflow action is pinned to a full commit SHA. It uses the standard
library only, so it needs no dependency install.
pr-title.ymlunchanged, and keep Dependabot for GitHub Actions anddependency-review.yml: the repository still has pinned actions to keepcurrent and to review.
dependency-review.ymlno longer runs onedited:with
cancel-in-progress, a PR body edit right after a push cancelled therun for that head and left a cancelled
Dependency reviewcheck on it.release workflow wrote tags and releases with a write token.
change; all actions stay pinned to full SHAs (the organization requires it).
correcting the three agent skills that still describe the publisher (a
separate PR in
atrinik/agent-integrations); theatrinik/.githubprofilepage; any GitHub setting.
Implementation / behavior
Removed:
bin/,lib/,tests/(publisher, planning publisher, Project sync,community-health generator, property publisher, audit, Project health
check, manual-settings verifier, security readiness and their tests).
community-health/, the source that used to generateatrinik/.github.That repository is now edited by hand through pull requests.
publish.yml,publish-planning.yml,sync-project.yml,check-project-health.yml,audit.ymlandrelease.yml(semantic release), plus
.releaserc.json,scripts/release/andrequirements-validation.txt.config/exceptplanning.json, includingconfig/rulesets/. See "Config files kept" below.Changed:
.github/workflows/check.yml: thePolicy validationjob now runspython3 .github/scripts/check_repository.pyafter a checkout withpersist-credentials: false, with a 5-minute timeout. The checkout stayspinned to the same full SHA.
.github/scripts/check_repository.py(new, about 140 lines, standardlibrary only): prints one line per problem and exits 1 if there are any.
It reads files only and never uses the network.
README.md,AGENTS.mdandCONTRIBUTING.md, rewritten to be short. Theysay what the repository is now; that the automation was retired on
2026-11-14 by owner decision, and why; that settings are changed by hand
under the owner's login and recorded here in the same task (until the
baseline lands, in the description of the pull request or task that made
the change); that the
Atrinik work board is no longer filled automatically; that
atrinik/.githubis edited by hand through pull requests; how the threerollouts that were never switched on are settled (required SHA pinning is
on; CodeQL as a merge requirement and the
playtestermerge queue aredropped); and that the history is in Git and in
v2.26.0.Unchanged:
config/planning.json,pr-title.yml,.github/dependabot.yml,LICENSE,.gitattributes,.gitignore.dependency-review.ymlchangesonly its trigger list (drops
edited).Config files kept
Before deleting the config files I looked for anything else that reads them:
gh search code --owner atrinik "github-settings"(37 hits, allinspected) and a search per config file name.
~/.claude/plugins/cache,~/.codex/plugins,/opt/agent-baseline) for each file name.config/planning.jsonatrinik-developmentskillsatrinik-issue-delivery(references/preparation.md) andatrinik-program-delivery(SKILL.md) read its Status names, fromatrinik/agent-integrationsand from the installed plugin caches.config/*.jsonandconfig/rulesets/*.jsongithub-settingsonly as a repository name, in prose or in pinned checkout lists.Validation
python3 .github/scripts/check_repository.py: passes on this branch.reference-style and HTML relative links, and an
actions/checkout@v4and adocker://tag reference were each reported. Links inside code spans andfences, anchors, URLs and links to directories were not.
git diff --check: clean.workflow change is one job with two steps.
rendering: headings, links and the table render.
ca44cf5changes onlyREADME.mdandAGENTS.md;the check passes on it.
356c1fechanges only thedependency-review.ymltrigger list; the check and
git diff --checkpass on it.c33e9e9):Policy validation,Conventional PR title,Dependency review, CodeQLAnalyze (actions)andAnalyze (python)pass. CodeQLAnalyze (javascript-typescript)fails;see below.
Limitations / follow-up
Analyze (javascript-typescript)fails on this branch. The repository'sCodeQL default setup still lists JavaScript/TypeScript, and the only
JavaScript files were the semantic-release scripts this PR removes, so
CodeQL reports that it "could not process any code written in
JavaScript/TypeScript" (and the
CodeQLcheck is neutral with"1 configuration not found"). No ruleset requires that check, so GitHub
would allow the merge, but the delivery gate (
pr-gate ready) treats anyfailing check as blocking, so this PR stays in draft until it is resolved.
After merge, every push to
mainwould fail the same analysis. The fix is arepository setting this PR may not change: the owner either drops
JavaScript/TypeScript from the default-setup languages (keeping
actionsand
python), recorded in the same task, or accepts the check as advisoryfor this PR. Adding JavaScript just to give CodeQL something to scan was
rejected as a workaround.
atrinik-developmentskills still describe the publisher andpoint at the old
AGENTS.md. A separate pull request inatrinik/agent-integrationscorrects them.atrinik/atrinik'ssupply-chain/inventory.jsonlistsgithub-settingsinthe scope of
actions/setup-node, which onlyrelease.ymlused. Its fullsupply-chain audit compares inventory scope with real use, so it will report
missing=['github-settings']for that action until the inventory is updatedthere.
request to this repository.
v2.26.0stays the last one.🤖 Generated with Claude Code