ci: Extract manifest specs from workflow to config.yml #494
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During recent CI additions, explanatory comments were removed from build scripts, and manifest configuration remained embedded in the workflow file instead of being extracted to config like the path detection logic.
Changes
Restored comments in
docker/linux/build.shdebian_build.shstyle (Ubuntu config, multi-arch setup, variant logic, default target)Restructured
.github/config.ymlschemaEach distro is now a top-level key with nested
ci.paths(for path-based detection) andmanifests(for OCI specs) sections, making the configuration more intuitive and self-contained.Updated
.github/workflows/build.yml.debian.manifests | map(. + {tag: (.tag | gsub("{sha}"; "..."))}) | {manifests: .}.debian.ciand.ubuntu.ci.debian.manifestsand.ubuntu.manifestsManifest configs use
{sha}placeholder for runtime substitution instead of inline template expansion.Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.