Skip to content

[CI][format] Explicitly pass extensions to git-clang-format #95794

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

Merged
merged 2 commits into from
Jun 17, 2024

Conversation

ldionne
Copy link
Member

@ldionne ldionne commented Jun 17, 2024

This ensures that the CI script controls which file extensions are considered instead of letting git-clang-format apply its own filtering rules. In particular, this properly handles libc++ extension-less headers which were passed to git-clang-format, but then dropped by that tool as having an unrecognized extension.

This ensures that the CI script controls which file extensions are
considered instead of letting git-clang-format apply its own filtering
rules. In particular, this properly handles libc++ extension-less headers
which were passed to git-clang-format, but then dropped by that tool
as having an unrecognized extension.
@ldionne ldionne requested review from tru and philnik777 June 17, 2024 14:24
Copy link

github-actions bot commented Jun 17, 2024

✅ With the latest revision this PR passed the Python code formatter.

@tru
Copy link
Collaborator

tru commented Jun 17, 2024

Please run black, other than that LGTM! It's a bit strange that even if you pass clang-format an explicit list it still filters it, but hey glad we have this workaround

@ldionne ldionne merged commit 7620fe0 into llvm:main Jun 17, 2024
4 of 6 checks passed
@ldionne ldionne deleted the review/fix-clang-format-extensionless branch June 17, 2024 20:21
boomanaiden154 added a commit to boomanaiden154/llvm-project that referenced this pull request Jun 28, 2024
boomanaiden154 added a commit that referenced this pull request Jun 28, 2024
…95794)"

This reverts commit 7620fe0.

This patch was causing some significant portion of code formatting jobs
to succeed when they should have failed. More investigation is needed.

Tracked in #97060.
@boomanaiden154
Copy link
Contributor

@ldionne This was causing a reasonably significant portion of formatting failures to not get caught. See #97060. I've reverted for now.

lravenclaw pushed a commit to lravenclaw/llvm-project that referenced this pull request Jul 3, 2024
…lvm#95794)"

This reverts commit 7620fe0.

This patch was causing some significant portion of code formatting jobs
to succeed when they should have failed. More investigation is needed.

Tracked in llvm#97060.
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