-
-
Notifications
You must be signed in to change notification settings - Fork 0
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:
jeremylongworth-source/ChefSkills - Visibility: public
- Default branch:
main - Wiki: enabled
- Issues: enabled
- Wiki editing: restricted to collaborators unless governance changes deliberately
main requires:
- the
Validate ChefSkillsstatus 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.
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.
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.
- Keep scope small and reviewable.
- Run
.\scripts\validate-all.ps1. - Run
gh skill publish --dry-run. - Confirm GitHub Actions passes.
- Update the changelog and release notes.
- Tag from a validated commit.
- Publish with
gh skill publish --tag <version>when the release should be installable throughgh skill. - Publish or update the GitHub Release.
- Record launch-state changes in
docs/audits/.
The GitHub wiki is a separate git repository:
git clone https://github.com/jeremylongworth-source/ChefSkills.wiki.gitCommit 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.
ChefSkills v0.1.0-public-preview is public-alpha software. Safety-sensitive culinary guidance requires current authoritative source checks and conservative uncertainty handling.