Code generation
GitHub Actions + GitLab CICI and repository quality
Generated components include repeatable CI definitions and repository-local quality gates.
When to use
Use this reference when generating, reviewing or operating a Service Architect project.
Behavior
- Root workflows validate the complete language workspace.
- Service/package workflows validate components as independent repositories.
- GitLab CI files provide an equivalent generated entrypoint.
- Dependabot configuration is emitted where the component ecosystem supports it.
- act and .actrc allow GitHub workflows to run locally in Docker.
- Generated git hooks run lint before commit and tests before push when installed.
CI and quality files
Repository automation generated at root and component scope.
FilePurposeDescription
.github/workflows/*generated.ymlGenerated root CILanguage workspace checks such as C++ or TypeScript CI.
<service>/.github/workflows/ci.ymlManaged component CIStandalone service build, test and lint.
<package>/.github/workflows/ci.generated.ymlGenerated package CIIndependent contract/model verification.
.gitlab-ci.ymlPreserved/managedGitLab pipeline entrypoint.
.gitlab-ci.*.generated.ymlGenerated root CILanguage-specific GitLab jobs.
<component>/.github/dependabot.ymlGenerated policyDependency update configuration.
.actrcManagedDefaults for running GitHub Actions locally.
scripts/pre-commit.generated.shGenerated hookRepository lint quality gate.
scripts/pre-push.generated.shGenerated hookRepository test quality gate.
.editorconfig + formatter configsManagedCross-editor and language formatting policy.
.gitignore + .dockerignoreManagedGenerated repository and image context exclusions.
Local quality pipeline
make tools
make ci
make act
cd <service-name> && make hooks