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

Use new clang-format in CI #518

Merged
merged 1 commit into from
Jan 6, 2025
Merged

Use new clang-format in CI #518

merged 1 commit into from
Jan 6, 2025

Conversation

JelteF
Copy link
Collaborator

@JelteF JelteF commented Jan 3, 2025

In #496 we started using the newest clang-format to format our files,
but CI was still installing the old version. This meant that we were not
catching some unformatted files correctly. An example of this being:
#511 (comment)

This starts using the correct clang-format version in CI too and formats
any incorrectly formatted files.

In #496 we started using the newest clang-format to format our files,
but CI was still installing the old version. This meant that we were not
catching some unformatted files correctly. An example of this being:
#511 (comment)

This starts using the correct clang-format version in CI too and formats
any incorrectly formatted files.
@JelteF JelteF mentioned this pull request Jan 3, 2025
@Y-- Y-- merged commit 4fdaad1 into main Jan 6, 2025
5 checks passed
@Y-- Y-- deleted the use-new-clang-format-in-ci branch January 6, 2025 08:47
ritwizsinha pushed a commit to ritwizsinha/pg_duckdb that referenced this pull request Jan 11, 2025
In duckdb#496 we started using the newest clang-format to format our files,
but CI was still installing the old version. This meant that we were not
catching some unformatted files correctly. An example of this being:
duckdb#511 (comment)

This starts using the correct clang-format version in CI too and formats
any incorrectly formatted files.
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