Skip to content

Maintainer Operations

Jeremy Longworth edited this page Sep 12, 2026 · 3 revisions

Maintainer Operations

This page summarizes the repository controls and release workflow for the public-alpha project.

Source check: docs/audits/2026-09-03-public-launch-check.md

Repository settings

  • Repository: jeremylongworth-source/ChefSkills
  • Visibility: public
  • Default branch: main
  • Wiki: enabled
  • Issues: enabled
  • Wiki editing: restricted to collaborators unless governance changes deliberately

Branch protection

main requires:

  • the Validate ChefSkills status check
  • strict status checks
  • one pull request approval
  • stale review dismissal
  • conversation resolution
  • linear history
  • no force pushes
  • no branch deletion

Admin enforcement is disabled so the maintainer can recover the repository when needed. Any release-relevant bypass should be documented in the relevant task or audit.

CI

The Validate workflow runs on pull requests, pushes to main, and manual dispatch. It uses pinned GitHub Actions releases and runs ./scripts/validate-all.ps1.

Security and maintenance

Enabled controls include Dependabot alerts, security updates, automated security fixes, GitHub Actions version updates, secret scanning, and secret-scanning push protection.

The repository has no package dependency manifest or lockfile. Current dependency maintenance is therefore focused on GitHub Actions.

Release workflow

  1. Keep scope small and reviewable.
  2. Run .\scripts\validate-all.ps1.
  3. Run gh skill publish --dry-run.
  4. Confirm GitHub Actions passes.
  5. Update the changelog and release notes.
  6. Tag from a validated commit.
  7. Publish with gh skill publish --tag <version> when the release should be installable through gh skill.
  8. Publish or update the GitHub Release.
  9. Record launch-state changes in docs/audits/.

Wiki workflow

The GitHub wiki is a separate git repository:

git clone https://github.com/jeremylongworth-source/ChefSkills.wiki.git

Commit wiki edits inside the wiki checkout and push them to make pages live. Keep the wiki aligned with the repository README, setup docs, roadmap, and release state.

Clone this wiki locally