Conversation
Feature work lands on dev, and until now nothing checked it: CI only triggered for main. The image build and publish jobs stay gated on a push to main. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
|
Closing: CI on dev is being handled in a separate change that also adds the integration tests. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
CI only triggered for
main, so every pull request intodevmerged with no checks at all. This runs the Rust and frontend jobs for pull requests intodevand for pushes todev. The image build and publish jobs keep theirpushtomaingate, so nothing is published fromdev.The integration suite is still
#[ignore]d in CI; that is unchanged here.🤖 Generated with Claude Code