-
Notifications
You must be signed in to change notification settings - Fork 120
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
clang-format isn't being properly enforced #305
Milestone
Comments
Yeah we used to have a format checker.
Please flag junrui to resurrect it. We have move to GitHub ci and away from
maintaining our own Jenkins server.
…On Tue, Jun 4, 2024 at 14:26 Aaron Barnes ***@***.***> wrote:
I don't think the method setup in #236
<#236> is properly
enforcing clang-format, because the dev branch has already diverged quite a
bit from the formatting (I ran it on the latest dev commit and there are
quite a few changes
https://github.com/barnes88/gpgpu-sim_distribution/tree/clang-format-6.4.24).
This is annoying if you have your editor set to enforce formatting on save,
because it causes a bunch of lines to be changed that you didn't edit.
Maybe we can have Jenkins run a formatting stage diff so we can reject PRs
that aren't properly formatted. Or we need everyone in the lab to install
the pre-commit hooks.
@FJShen <https://github.com/FJShen>
—
Reply to this email directly, view it on GitHub
<#305>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA7UY4NLUNNOGKXO4B4WRSDZFYBFLAVCNFSM6AAAAABIZBLXCKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZTIMJSG42TGOI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Or I can spawn a job to run the format script before merge. |
@JRPan do you have anything implemented for the automatic formatting? |
Should we do automatic formatting before merging? Or reject non-formatted PR and ask people to format it? |
I think having automatic formatting would be easiest, that way people don't have to worry about trying to match the version of clang-format |
This was referenced Jul 13, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I don't think the method setup in #236 is properly enforcing clang-format, because the dev branch has already diverged quite a bit from the formatting (I ran it on the latest dev commit and there are quite a few changes https://github.com/barnes88/gpgpu-sim_distribution/tree/clang-format-6.4.24). This is annoying if you have your editor set to enforce formatting on save, because it causes a bunch of lines to be changed that you didn't edit.
Maybe we can have Jenkins run a formatting stage diff so we can reject PRs that aren't properly formatted. Or we need everyone in the lab to install the pre-commit hooks.
@FJShen
The text was updated successfully, but these errors were encountered: