VARASYS/ZDDC
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(ci): single-line commit messages in notify workflows (YAML pipe block)

Browse source 
Multi-line git commit message bodies broke YAML parsing — pipe blocks
end on unindented lines, so the body lines starting at column 0 were
being interpreted by Forgejo's YAML parser as keys, yielding:

  yaml: line 158: could not find expected ':'

Switch to repeated `-m` flags (one per paragraph). Same end result
in git log; valid YAML.
This commit is contained in:
ZDDC 2026-05-03 18:38:25 -05:00
parent b47b5222af
commit 2820dffeaa
2 changed files with 10 additions and 22 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
.forgejo/workflows/deploy-release.yml
View file

@ -153,16 +153,9 @@ jobs:
git config user.name "ZDDC Release Bot" git config user.name "ZDDC Release Bot"
git config user.email "noreply@zddc.varasys.io" git config user.email "noreply@zddc.varasys.io"
git add chart/Chart.yaml git add chart/Chart.yaml
git commit -m "chore(chart): auto-bump appVersion to $VERSION (ZDDC stable cut) git commit \
-m "chore(chart): auto-bump appVersion to $VERSION (ZDDC stable cut)" \
Triggered by zddc-server-v$VERSION tag push on git.varasys.io/VARASYS/ZDDC. -m "Triggered by zddc-server-v$VERSION tag push on git.varasys.io/VARASYS/ZDDC. Bumps appVersion so the prod Docker image is tagged zddc:$VERSION, ensuring kubelet pulls a fresh image on the next helm upgrade. Chart version bumped to $NEW_CHART_VER (patch) so JFrog has a clean chart history per deploy." \
Bumps Chart.yaml so the prod Docker image is tagged \`zddc:$VERSION\`, -m "Auto-generated by .forgejo/workflows/deploy-release.yml's notify-chart-prod job. Do not edit manually — the next ZDDC stable cut will overwrite this commit's changes."
ensuring kubelet pulls a fresh image on the next helm upgrade. Chart
\`version\` bumped to $NEW_CHART_VER (patch) so JFrog has a clean
chart history per deploy.
Auto-generated by .forgejo/workflows/deploy-release.yml's
notify-chart-prod job. Do not edit manually — the next ZDDC stable
cut will overwrite this commit's changes."
git push origin main git push origin main
echo "✓ pushed chart appVersion bump → BMCD pipeline-prod will fire" echo "pushed chart appVersion bump - BMCD pipeline-prod will fire"

15
.forgejo/workflows/notify-chart-dev.yml
View file

@ -92,14 +92,9 @@ jobs:
git config user.name "ZDDC Release Bot" git config user.name "ZDDC Release Bot"
git config user.email "noreply@zddc.varasys.io" git config user.email "noreply@zddc.varasys.io"
git add chart/Chart.yaml git add chart/Chart.yaml
git commit -m "chore(chart): auto-bump appVersion to $BETA_VERSION (ZDDC beta cut) git commit \
-m "chore(chart): auto-bump appVersion to $BETA_VERSION (ZDDC beta cut)" \
Triggered by push to git.varasys.io/VARASYS/ZDDC main with -m "Triggered by push to git.varasys.io/VARASYS/ZDDC main with embedded/* changes (a ./build beta cut). Bumps appVersion so the dev Docker image is tagged zddc:$BETA_VERSION, ensuring kubelet pulls a fresh image on the next helm upgrade." \
embedded/* changes (a \`./build beta\` cut). Bumps Chart.yaml so -m "Auto-generated by .forgejo/workflows/notify-chart-dev.yml. The next ZDDC beta or stable cut will overwrite this."
the dev Docker image is tagged \`zddc:$BETA_VERSION\`, ensuring
kubelet pulls a fresh image on the next helm upgrade.
Auto-generated by .forgejo/workflows/notify-chart-dev.yml. The
next ZDDC beta or stable cut will overwrite this."
git push origin develop git push origin develop
echo "✓ pushed chart develop bump → BMCD pipeline-dev will fire" echo "pushed chart develop bump - BMCD pipeline-dev will fire"