Repository navigation
chore(ci): clean up old duplicate workflows - #362
Merged
Merged
Conversation
skylarmb
enabled auto-merge (squash)
May 19, 2026 23:11
nebrius
approved these changes
May 19, 2026
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
2 participants
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.
Equivalent (newer and more robust) integration test and unit test workflows run on internal CI on every commit. These workflows in the public repo have drifted and are breaking just due to differences in environment setup (
uvvspython, live staging API vs dedicated integration test harness, repo secrets, etc.). They are an artifact from before we switched to managing source code in our internal repo.