0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-12 13:47:01 +00:00

Files

T

kevinveenbirkenbachandClaude Opus 4.8 b9d86e176f test(lint): fail on invalid git branch names

Add tests/lint/repository/naming/test_branch_name.py validating the checked-out branch against the naming policy in branch.md. Rejects unknown prefixes (e.g. feat/ instead of feature/), non-kebab-case descriptions, and fix/ branches missing a ticket id; exempts main, master, and detached HEAD. Document the local enforcement in branch.md.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

2026-06-28 21:13:46 +02:00

actions

test(variants): enforce shared DB providers via shared-false-once lint

2026-06-26 20:37:35 +02:00

artefact

test(lint): fail on invalid git branch names

2026-06-28 21:13:46 +02:00

design

feat(deploy): always run the full variant matrix (remove runtime time-cut)

2026-06-23 02:50:56 +02:00

environment

fix(compose-deploy): stop persisting runtime routing knobs into .env

2026-05-28 17:47:03 +02:00

organisation

docs: fix repo-wide drift against documentation.md style rules

2026-05-15 20:12:07 +02:00

tools

ci(fork): key trusted fork PRs off the '🛡️ Trusted' label

2026-06-28 19:58:54 +02:00

documentation.md

refactor: drop requirement-file references from code, add doc rule + lint

2026-05-10 16:25:22 +02:00

index.rst

docs(contributing): apply documentation.md rules across all staged files

2026-04-10 21:06:17 +02:00

README.md

docs: add scope README docs under docs

2026-04-10 17:23:10 +02:00

requirements.md

docs(changelog): per-release archive CLI + release docs + SPOT cleanup

2026-05-08 16:19:42 +02:00

workflow.md

docs(contributing): apply documentation.md rules across all staged files

2026-04-10 21:06:17 +02:00

README.md

Contribution documentation 🤝

This directory contains contributor-facing repository rules and workflows. Its scope is how humans and agents set up the environment, write documentation, communicate, define requirements, and contribute safely through the project lifecycle.