Repository navigation
drift: auto-merge when core.ts is unchanged and checks pass - #11
Merged
Merged
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
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.
When the weekly drift run finds an upstream release whose
core.tsis identical to the vendored one and every check in the workflow passed, it now dispatchesci.ymlon the branch and sets the PR to auto-merge. PRs opened with the workflow token do not start CI, so the dispatch is what satisfies the required checks (check (20),check (22),integration).actions: writeso the workflow can dispatch CI.core.tsdiff, or a failed check, still leaves the PR for manual review.Not covered:
schemas.jsoncan change without acore.tschange; it only affectswf schemaoutput. Not tested end to end, since that needs a new upstream release with an unchangedcore.ts. Watch the first one.