Skip to content

chore: retire the settings publisher, sync and audit - #106

Merged
zoeyrose merged 4 commits into
mainfrom
chore/retire-settings-tooling
Nov 14, 2026
Merged

zoeyrose merged 4 commits into
mainfrom
chore/retire-settings-tooling

Conversation

@zoeyrose

@zoeyrose zoeyrose commented Nov 14, 2026 •

Copy link
Copy Markdown
Member

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.json and a small
CI 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

  • Goal: make the retired publisher, sync and audit impossible to run from
    this repository, and replace the long desired-state documentation with a
    short, accurate description of what the repository is now.
  • Decisions and why:
    • Remove bin/, lib/, tests/, community-health/, the release scripts
      and 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 main commit).
    • Keep config/planning.json byte for byte. Three atrinik-development
      agent skills read its Project Status names.
    • Keep both required check names: the ruleset 03 - Required CI - github-settings requires Policy validation and Conventional PR title.
      Policy validation becomes a small real check: every tracked JSON file
      parses, 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.
    • Keep pr-title.yml unchanged, and keep Dependabot for GitHub Actions and
      dependency-review.yml: the repository still has pinned actions to keep
      current and to review. dependency-review.yml no longer runs on edited:
      with cancel-in-progress, a PR body edit right after a push cancelled the
      run for that head and left a cancelled Dependency review check on it.
    • Remove semantic release. Nothing here is released any more, and the
      release workflow wrote tags and releases with a write token.
  • Constraints: no history rewrite; no tag, release or repository-setting
    change; all actions stay pinned to full SHAs (the organization requires it).
  • Out of scope: the settings check and Atrinik's baseline file (later PR);
    correcting the three agent skills that still describe the publisher (a
    separate PR in atrinik/agent-integrations); the atrinik/.github profile
    page; 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 generate atrinik/.github.
    That repository is now edited by hand through pull requests.
  • Workflows publish.yml, publish-planning.yml, sync-project.yml,
    check-project-health.yml, audit.yml and release.yml
    (semantic release), plus .releaserc.json, scripts/release/ and
    requirements-validation.txt.
  • Every file in config/ except planning.json, including
    config/rulesets/. See "Config files kept" below.

Changed:

  • .github/workflows/check.yml: the Policy validation job now runs
    python3 .github/scripts/check_repository.py after a checkout with
    persist-credentials: false, with a 5-minute timeout. The checkout stays
    pinned to the same full SHA.
  • .github/scripts/check_repository.py (new, about 140 lines, standard
    library 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.md and CONTRIBUTING.md, rewritten to be short. They
    say 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/.github is edited by hand through pull requests; how the three
    rollouts that were never switched on are settled (required SHA pinning is
    on; CodeQL as a merge requirement and the playtester merge queue are
    dropped); 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.yml changes
only 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, all
    inspected) and a search per config file name.
  • A grep of this machine's agent skills (~/.claude/plugins/cache,
    ~/.codex/plugins, /opt/agent-baseline) for each file name.
File Kept? Why
config/planning.json Kept, unchanged atrinik-development skills atrinik-issue-delivery (references/preparation.md) and atrinik-program-delivery (SKILL.md) read its Status names, from atrinik/agent-integrations and from the installed plugin caches.
Every other config/*.json and config/rulesets/*.json Removed No reader outside this repository's own retired tools. Other repositories mention github-settings only as a repository name, in prose or in pinned checkout lists.

Validation

  • python3 .github/scripts/check_repository.py: passes on this branch.
  • Negative run in a scratch copy: a malformed JSON file, missing, outside-repo,
    reference-style and HTML relative links, and an actions/checkout@v4 and a
    docker:// tag reference were each reported. Links inside code spans and
    fences, anchors, URLs and links to directories were not.
  • git diff --check: clean.
  • actionlint is not installed on this machine, so it was not run locally. The
    workflow change is one job with two steps.
  • The rendered README and this body were checked through GitHub's HTML
    rendering: headings, links and the table render.
  • The follow-up commit ca44cf5 changes only README.md and AGENTS.md;
    the check passes on it.
  • The follow-up commit 356c1fe changes only the dependency-review.yml
    trigger list; the check and git diff --check pass on it.
  • CI on the first head (c33e9e9): Policy validation, Conventional PR title, Dependency review, CodeQL Analyze (actions) and
    Analyze (python) pass. CodeQL Analyze (javascript-typescript) fails;
    see below.

Limitations / follow-up

  • Owner decision needed before this PR can leave draft: CodeQL
    Analyze (javascript-typescript) fails on this branch.
    The repository's
    CodeQL 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 CodeQL check 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 any
    failing check as blocking, so this PR stays in draft until it is resolved.
    After merge, every push to main would fail the same analysis. The fix is a
    repository setting this PR may not change: the owner either drops
    JavaScript/TypeScript from the default-setup languages (keeping actions
    and python), recorded in the same task, or accepts the check as advisory
    for this PR. Adding JavaScript just to give CodeQL something to scan was
    rejected as a workaround.
  • The three atrinik-development skills still describe the publisher and
    point at the old AGENTS.md. A separate pull request in
    atrinik/agent-integrations corrects them.
  • atrinik/atrinik's supply-chain/inventory.json lists github-settings in
    the scope of actions/setup-node, which only release.yml used. Its full
    supply-chain audit compares inventory scope with real use, so it will report
    missing=['github-settings'] for that action until the inventory is updated
    there.
  • The read-only settings check and Atrinik's baseline come in a later pull
    request to this repository.
  • After merge, nothing here creates releases. v2.26.0 stays the last one.

🤖 Generated with Claude Code

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>
@github-actions

github-actions Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues found.

Scanned Files

  • .github/workflows/publish-planning.yml
  • .github/workflows/sync-project.yml
  • requirements-validation.txt

zoeyrose and others added 2 commits November 14, 2026 13:20
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>
@zoeyrose

Copy link
Copy Markdown
Member Author

Self-review

Reviewed by fresh-context independent reviewer subagents, each given the intent brief:

  • Round 0: full diff at c33e9e95771aba788fd3ad764bd003ee40c65f2f and the code it touches.
  • Round 1: delta c33e9e9..ca44cf5f45e25bfd498c95e0e4836bc27e55bd6c.
  • Round 2: delta ca44cf5..356c1fead30e4ab86b0416f0dfe419db093a3ae8. No findings.

The current head 356c1fead30e4ab86b0416f0dfe419db093a3ae8 is the head reviewed in round 2; there are no unreviewed commits.

Findings

  • P1 (round 0): CodeQL Analyze (javascript-typescript) fails because the diff removes the repository's only JavaScript while default setup still lists javascript/typescript, so pr-gate ready is blocked. Not fixable in this PR within its rules (the cause is a repository setting this task may not change; adding JS just to feed CodeQL would be a workaround). The PR body now states that an owner decision is needed before this PR can leave draft, with the two options.
  • P3 (round 0): AGENTS.md told agents to record settings changes in this repository before any record file exists. Fixed in ca44cf5 (interim rule in AGENTS.md and README.md).
  • P2 (round 1): a PR body edit right after a push cancelled the Dependency review run on the head, which the gate counts as a failure. Fixed in 356c1fe (dropped edited from the workflow's pull_request types).
  • Round 2: no findings.

@zoeyrose zoeyrose closed this Nov 14, 2026
@zoeyrose zoeyrose reopened this Nov 14, 2026
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>
@zoeyrose

Copy link
Copy Markdown
Member Author

Reviewed head 13ec81fe5d51012a04e8543411d75110f39864a7.

This head adds one empty commit on top of 356c1fead30e4ab86b0416f0dfe419db093a3ae8, which fresh-context independent reviewers covered in three rounds (the last with no findings; see the previous receipt). git diff 356c1fe 13ec81fe5d51012a04e8543411d75110f39864a7 is empty, checked by the coordinating session.

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 actions and python. The failed run could not be retried, so an empty commit gives the pull request a head without the stale result.

No findings; no content changed since the last reviewed head.

@zoeyrose
zoeyrose marked this pull request as ready for review November 14, 2026 19:29
@zoeyrose zoeyrose self-assigned this Nov 14, 2026
@zoeyrose
zoeyrose requested a review from a team November 14, 2026 19:29
@zoeyrose
zoeyrose merged commit b74a20d into main Nov 14, 2026
6 checks passed
@zoeyrose
zoeyrose deleted the chore/retire-settings-tooling branch November 14, 2026 19:30
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.

1 participant