Merged
Conversation
Member
|
Although, note that I think there's two issues going on: #1429 (comment) |
Member
Author
|
Thanks @davisp ! We'll at least get this first half addressed. |
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.
Which issue does this PR close?
Addresses half of #1429
Rationale for this change
The crates patch check only needs to occur during releases and release candidates. These are triggered by the tag push. Do not run this check on merges to main.
What changes are included in this PR?
CI update to not run check on merge to main.
Drive by update to reduce build time by not pulling submodules.
Are there any user-facing changes?
No, CI only