Open
Conversation
josephjclark
force-pushed
the
tracking-deploy-bug
branch
from
4b0e5cd to
0a42b8d
Compare
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.
Branch to try and track bugs on deploy.
Looking at Farhan's integration tests it looks like
a) unchanged local workflows will overwrite remote changed workflows - but I've seen this working in the CLI!!
b) the CLI incorrectly warns that unchanged local workflows have changed - but again this used to work!
I'm sure I keep fixing and then breaking this stuff. The new integration tests are cool but hard to debug. So trying to add new unit tests to help me track down the problems (and keep them tracked!!)
AI Usage
Please disclose whether you've used AI anywhere in this PR (it's cool, we just
want to know!):
You can read more details in our
Responsible AI Policy