Skip to content

Conversation

@sbomer
Copy link
Member

@sbomer sbomer commented Apr 1, 2022

Fixes new headers which were causing the build to fail after 4f0d349.

@sbomer sbomer requested a review from marek-safar as a code owner April 1, 2022 17:52
@sbomer sbomer requested review from jtschuster and tlakollo April 1, 2022 17:52
@jtschuster
Copy link
Member

Thanks for catching this! Is this check not run on all PRs before they merge?

@tlakollo
Copy link
Contributor

tlakollo commented Apr 1, 2022

Thanks for catching this! Is this check not run on all PRs before they merge?

It does but your CI run, ran before the change was merged. Unless running a second time it wouldn't be possible to detect. Sorry for not informing you before

@sbomer
Copy link
Member Author

sbomer commented Apr 1, 2022

This can happen because PRs run against a merge commit that's created against main at the time that the PR is made. If main is later updated, the PRs don't get re-run on a new merge commit. Sometimes that kind of situation is caught by merge conflicts, but sometimes (like here) there's no visible merge conflict.

@sbomer sbomer merged commit 49e147b into dotnet:main Apr 1, 2022
@sbomer sbomer deleted the fixNewHeaders branch April 14, 2022 18:33
agocke pushed a commit to dotnet/runtime that referenced this pull request Nov 16, 2022
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.

3 participants