Skip to content

Keep affected running after merged PRs when Publish or Deploy reads it - #103

Merged
russwyte merged 1 commit into
mainfrom
fix/skip-merged-pr-affected-102
Aug 12, 2026
Merged

Keep affected running after merged PRs when Publish or Deploy reads it#103
russwyte merged 1 commit into
mainfrom
fix/skip-merged-pr-affected-102

Conversation

@russwyte

Copy link
Copy Markdown
Contributor

Summary

  • skipMergedPrPush was skipping the Verify-shaped affected job, so Graph Publish/Deploy started with an empty needs.affected.outputs.modules and fromJson("") failed the workflow template.
  • Same treatment as tag pushes: when Graph Publish or Deploy reads affected, that job stays up on a merged-PR push and emits ["all"]. Graph Verify jobs carry their own verify-gate clause instead of inheriting the skip through affected.
  • Closes skipMergedPrPush skips affected, so Publish/Deploy fromJson an empty output on merged-PR main pushes #102.

Test plan

  • sbt "core/testFull; docs/testFull"
  • sbt scalafmtCheckAll
  • After the next zipx release is consumed: merge a green PR to main on a repo with Graph docker + skipMergedPrPush (optimize-frequency is the failing fixture). Expect affected green with ["all"], Verify skipped, docker/deploy actually running, no JsonReaderException.

skipMergedPrPush was skipping the Verify-shaped affected job, so Graph
Publish/Deploy fromJson an empty output. Mirror the tag-push treatment:
affected stays up and emits ["all"], and Graph Verify carries its own gate.
@russwyte
russwyte merged commit 8360aea into main Aug 12, 2026
6 checks passed
@russwyte
russwyte deleted the fix/skip-merged-pr-affected-102 branch August 12, 2026 22:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

skipMergedPrPush skips affected, so Publish/Deploy fromJson an empty output on merged-PR main pushes

1 participant