-
Notifications
You must be signed in to change notification settings - Fork 304
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
DAOS-16923 cq: make clang-format required #15685
base: master
Are you sure you want to change the base?
Conversation
Make clang-format GHA required on PRs. Skip-build: true Signed-off-by: Dalton Bohning <[email protected]>
Ticket title is 'Make clang-format required on PRs' |
@mchaarawi Per request, it's this simple to make clang-format required. Should we alert devs before merging this? |
Note that since this is version controlled, inflight PRs will not be affected until this change is merged into their branch |
Skip-build: true Signed-off-by: Dalton Bohning <[email protected]>
Since it may conflict with system. Skip-build: true Signed-off-by: Dalton Bohning <[email protected]>
Skip-build: true Signed-off-by: Dalton Bohning <[email protected]>
I think you're going to get some pushback internally on this one. I'm personally ok with it. |
If it's required, does it mean a PR has to be force landed. You might want to add or point to documentation for the comments to disable it (such as for FOREACH macros) when it does weird things. |
Right. It either needs to pass or needs force landing.
I don't work with C code enough to know - do you have an example of this? Or do you mean disable the hook with DAOS_GITHOOK_SKIP? (which would then require force landing) |
Make clang-format GHA required on PRs.
Skip-build: true
Before requesting gatekeeper:
Features:
(orTest-tag*
) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.Gatekeeper: