oblachno-oss/grm
3
0
Fork 0
Code Issues 23 Pull Requests 2 Actions Packages Projects Releases 16 Wiki Activity

GRM-52: fix: badges job runs after release to reflect actual state

Browse Source
This commit is contained in:
emil
2026-06-22 06:15:33 +00:00
parent b6e87a519b
commit 8bde4cd12b
5 changed files with 106 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tech/ci-cd-workflow.md
+9 -6
View File
@@ -233,13 +233,16 @@ are skipped — the tag push triggers the publish workflow instead.
The `badges` job in the post-merge workflow runs
`scripts/ci/push_badges.py` which:
1. Generates quality badge SVG files via `scripts/generate_badges.py`
2. Creates an orphan `badges` branch
3. Copies SVG files to the branch root
4. Force-pushes the branch to the remote
1. Fetches the latest master and hard-resets to it (picks up release commits)
2. Generates quality badge SVG files via `scripts/generate_badges.py`
3. Creates an orphan `badges` branch
4. Copies SVG files to the branch root
5. Force-pushes the branch to the remote
This replaces the previous inline shell script with a tested Python
equivalent that handles all git operations in a single script.
The badges job depends on the `release` job and uses `if: always()` so it
runs even if release fails or is skipped. This ensures the version badge
always reflects the actual state of the repository after any release
commits have been pushed.
## git-cliff Commit Preprocessing