ci: rename caller job ids to avoid colliding with reusable workflow's inner job name #7

Merged

james merged 1 commit from fix/security-scan-job-id-collision into main

2026-09-06 22:35:10 +00:00

james commented

2026-09-06 22:34:18 +00:00

Owner

Same fix as colibrisec/balam#15 -- the "two scans running" appearance is one wrapper job (near-zero duration) plus one real execution, both named scan (same for renovate), disambiguated by Forgejo as scan/scan-1. Renaming the caller job ids removes the collision.

Same fix as colibrisec/balam#15 -- the "two scans running" appearance is one wrapper job (near-zero duration) plus one real execution, both named `scan` (same for `renovate`), disambiguated by Forgejo as `scan`/`scan-1`. Renaming the caller job ids removes the collision.

james added 1 commit

2026-09-06 22:34:34 +00:00

ci: rename caller job ids to avoid colliding with reusable workflow's inner job name

test / test (pull_request) Successful in 33s

Details

security-scan / scan (pull_request) Successful in 2m2s

Details

security-scan / security-scan (pull_request) Successful in 0s

Details

2544d9c074

Both files' caller job was named the same as the reusable workflow's own
inner job (scan/scan, renovate/renovate). Forgejo's reusable-workflow
expansion lists both as sibling rows in the run, and since the names
collided it suffixed the second one -1 -- reading as two separate scans
running when it's actually one wrapper job (near-zero duration) plus one
real execution. Renaming the caller job id removes the collision.

james merged commit 0fd2a0ef3d into main

2026-09-06 22:35:10 +00:00

james deleted branch fix/security-scan-job-id-collision

2026-09-06 22:35:11 +00:00

james referenced this pull request from a commit

2026-09-06 22:35:11 +00:00

Merge pull request 'ci: rename caller job ids to avoid colliding with reusable workflow's inner job name' (#7) from fix/security-scan-job-id-collision into main