Templates & Conventions

Boilerplate templates

Each language template includes:

• Dependency manifest — e.g. Cargo.toml
• Entry point — boilerplate source file.
• README.md — with placeholders for name and description.
• .gitignore — language-specific (fetched from the GitHub API).
• .github/workflows/ci.yml — CI workflow with basic checks.
• .github/workflows/release.yml — release workflow (runs on git tags).
• LICENSE — fetched from the API based on the license selected during the wizard.

All files land in a single atomic chore: init repository commit.

Available today: Rust. Python, Node.js and Java are planned.

Standard labels

7 labels are enforced on every repo. Non-standard labels are removed.

Branch protection

When enabled, ghscaff applies to the default branch (and develop when present):

• ✅ Require 1 approval before merging.
• ✅ Require status checks to pass (wired to the CI workflow).
• ✅ Dismiss stale reviews.
• ✅ Disallow force-push.

Secrets

Templates declare required GitHub Actions secrets in secrets.toml. Ghscaff resolves each one in order:

1. Encrypted vault — previously saved secrets.
2. Environment variable — e.g. CARGO_REGISTRY_TOKEN.
3. Interactive prompt — with the option to save to the vault.

For the Rust template:

• CARGO_REGISTRY_TOKEN — required for publishing to crates.io (get one here).