Automation & CI/CD
.gitea/ is the repository’s automation control folder: event-driven workflows and local actions that orchestrate the repository’s own commands.
.gitea/
2Trait
Behaves the same locally, in the development container, and on a CI runner.
.gitea/ is the repository’s automation control folder: event-driven workflows and local actions that orchestrate the repository’s own commands.
.gitea/
2An identical root Makefile in every repository, with the repository’s own components declared once in scripts/build/repository.mk.
Makefile
4A developer deployment names its instance from the Terraform workspace, chosen from an override, the CI branch, or the local username — never from a per-developer file.
workspaces/
3The authoritative development environment for a repository — reusable features provide the toolchains, and repository-specific lifecycle hooks finish the workspace.
.devcontainer/
4When a capability is intentionally unavailable, a command says so with a skip: line and succeeds, while a check that actually fails still exits non-zero.
scripts/
6One aggregate lint command runs every linter that is installed, skips the rest with a clear message, and fails only on real findings.
scripts/lint.sh
4Standard files copied into every repository carry a DO NOT EDIT header; they are changed at their source, never in the repository that received them.
./
0Small, focused infrastructure building blocks with explicit inputs and outputs, consumed by deployable roots in env/ and workspaces/.
modules/
3Repository tooling with stable command entry points and documented contracts — small applications that own a workflow, rather than glue around one.
tools/
2No specification matches every filter.