feat: add conditional step execution with skip infrastructure #572
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 736e5b4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
View your CI Pipeline Execution ↗ for commit 736e5b4
☁️ Nx Cloud last updated this comment at |
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
pkgs/core/supabase/migrations/20260105074725_pgflow_temp_skip_infrastructure.sql
Outdated
Show resolved
Hide resolved
This was referenced Jan 5, 2026
jumski
force-pushed
the
01-05-condition
branch
from
2c84deb to
ac6da93
Compare
jumski
force-pushed
the
01-05-condition
branch
from
ac6da93 to
74202cd
Compare
This was referenced Jan 8, 2026
This was referenced Jan 9, 2026
jumski
force-pushed
the
01-05-condition
branch
from
74202cd to
f0a6c8d
Compare
jumski
force-pushed
the
01-05-condition
branch
from
f0a6c8d to
9188cf6
Compare
jumski
force-pushed
the
01-05-condition
branch
from
9188cf6 to
b38ff13
Compare
jumski
force-pushed
the
01-05-condition
branch
from
b38ff13 to
963cad9
Compare
This was referenced Jan 22, 2026
- Add skip_type column and cascade_skip_steps() function - Add condition evaluation in start_ready_steps - Add whenFailed option for error handling after retries - Add ifNot negative condition pattern - Add ContainmentPattern<T> and StepMeta types for type-safe DSL - Add condition fields to FlowShape for auto-compilation
jumski
force-pushed
the
01-05-condition
branch
from
963cad9 to
736e5b4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add conditional execution infrastructure to pgflow
This PR adds support for conditional step execution in pgflow with a new "skip" infrastructure. The implementation includes:
New step configuration options:
condition_pattern: JSONB pattern for @> containment checkwhen_unmet: What to do when condition is not met (options: 'fail', 'skip', 'skip-cascade')when_failed: What to do when handler fails after retries (options: 'fail', 'skip', 'skip-cascade')New step status and tracking:
skip_reason,skipped_atto track why and when a step was skippedCascade functionality:
cascade_skip_stepsfunction to skip a step and all its downstream dependentsComprehensive test coverage:
This feature enables more flexible workflows where steps can be conditionally executed based on runtime data.