Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[macro_util] Rename from derive_util, include more #454

Merged
merged 1 commit into from
Oct 4, 2023
Merged

Conversation

joshlf
Copy link
Member

@joshlf joshlf commented Oct 4, 2023

Include macro utilities - namely, re-exports of core symbols used by macro-generated code.

Include macro utilities - namely, re-exports of core symbols used by
macro-generated code.
@joshlf joshlf requested a review from jswrenn October 4, 2023 00:07
@joshlf joshlf enabled auto-merge October 4, 2023 00:07
@joshlf joshlf added this pull request to the merge queue Oct 4, 2023
Merged via the queue into main with commit 55eb033 Oct 4, 2023
129 of 152 checks passed
@joshlf joshlf deleted the macro-utils branch October 4, 2023 00:18
@joshlf
Copy link
Member Author

joshlf commented Oct 4, 2023

Note: This was spuriously merged despite a CI failure due to a buggy merge queue configuration. I manually removed the commit from main and have re-submitted the PR as #455.

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants