[macro_util] Rename from derive_util, include more #454
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
Include macro utilities - namely, re-exports of core symbols used by macro-generated code.
jswrenn
approved these changes
Oct 4, 2023
Member
Author
|
Note: This was spuriously merged despite a CI failure due to a buggy merge queue configuration. I manually removed the commit from |
jswrenn
added a commit
that referenced
this pull request
Oct 4, 2023
Previously, a failing job could cause all-jobs-succeeded to be skipped, and branch protections interpreted a skipped job as being vacuously successful. This failure mode caused #454 to be merged to main, despite failing many CI checks. This PR inverts the `if` condition of this job: It only runs on failure, and upon failure, it fails.
jswrenn
added a commit
that referenced
this pull request
Oct 4, 2023
Previously, a failing job could cause all-jobs-succeed to be skipped, and branch protections interpreted a skipped job as being vacuously successful. This failure mode caused #454 to be merged to main, despite failing many CI checks. This PR inverts the `if` condition of this job: It only runs on failure, and upon failure, it fails.
jswrenn
added a commit
that referenced
this pull request
Oct 4, 2023
Previously, a failing job could cause all-jobs-succeed to be skipped, and branch protections interpreted a skipped job as being vacuously successful. This failure mode caused #454 to be merged to main, despite failing many CI checks. This PR inverts the `if` condition of this job: It only runs on failure, and upon failure, it fails.
jswrenn
added a commit
that referenced
this pull request
Oct 4, 2023
Previously, a failing job could cause all-jobs-succeed to be skipped, and branch protections interpreted a skipped job as being vacuously successful. This failure mode caused #454 to be merged to main, despite failing many CI checks. This PR inverts the `if` condition of this job: It only runs on failure, and upon failure, it fails.
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.
Include macro utilities - namely, re-exports of core symbols used by macro-generated code.