Repository navigation
Apply release automation configuration to Template_API_Repository #82
Description
Problem description
After the release automation is rolled out to existing API repositories via the onboarding campaign, the Template_API_Repository still lacks the release automation configuration. New API repositories created from the template will not inherit the full setup.
Possible evolution
Apply the release automation configuration to Template_API_Repository so that newly created API repositories inherit it automatically. This includes:
- Caller workflow (
.github/workflows/release-automation.yml) - CHANGELOG directory structure (
CHANGELOG/README.md) - Repository ruleset (
release-snapshot-protection) release-plan.yamltemplate with placeholder values
Note: GitHub repository rulesets are not inherited when creating a repository from a template. It is therefore important that new API repositories are created through the admin-api-repository-creation.yml workflow in project-administration, which ensures the ruleset gets copied from the template repository.
Alternative solution
Keep onboarding new repositories manually via the campaign workflow, but this adds unnecessary operational overhead for each new API repository.
Additional context
This should be done after the broader rollout of the release automation to existing repositories is complete and the configuration is considered stable. The onboarding campaign and admin script in project-administration (PR #134) can be reused for applying the configuration to the template.
See repository-setup.md for the full configuration specification.
Activity
hdamker commentedon Mar 1, 2026
Further changes are needed for the admin-api-repository-creation.yml workflow (create separate issue in project-administration)
hdamker commentedon Mar 3, 2026
Progress update (2026-03-03)
Template#32 has been merged, applying:
release-plan.yamltemplate with placeholder valuesCHANGELOG/directory structure (CHANGELOG/README.md)Remaining for GA:
.github/workflows/release-automation.yml) — deferred until the release automation reaches GA (@v1tag), so that new repositories don't inherit a workflow pointing at a pre-release versionrelease-snapshot-protection) — not inherited by GitHub template mechanism; applied via theadmin-api-repository-creation.ymlworkflow in project-administration, which already handles thisrelease-plan.yamlRelated: tooling#75 (repository setup documentation)
hdamker commentedon May 18, 2026
Done.
Template_API_Repositorynow carries the release-automation configuration:release-plan.yamltemplate, CODEOWNERS update, README pointersTemplate_API_Repositoryis in the onboarded set (v0 disabled). Closing.