-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sequencing CI effects #178
Comments
This feature has not been implemented yet. A workaround for your use case is to perform all publish actions in a single effect, which may also be slightly more efficient, by skipping setup like the Nonetheless, this feature should be implemented 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have a
cargoPublish
configured in a monorepo with multiple Rust crates, where A depends on B. When runningthe publish effect, I want B to be published first, otherwise publishing A would falis.
I know that cargo workspaces would be a solution, but in our architecture this is not an option.
Is there a way to sequence effects somehow?
The text was updated successfully, but these errors were encountered: