-
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-15677 cq: remove required-githooks watermark #15639
Conversation
Since it did not work in all scenarios and the GHA checks are more secure than client-side githooks. Skip-build: true Signed-off-by: Dalton Bohning <[email protected]>
Ticket title is 'add copyright GHA and remove required-githooks watermark' |
Before we remove the githook watermark, shouldn't we make the linting GHA checks required? |
They are :) I should have done this as one PR, but I thought pipeline-lib had some logic I needed to remove first (I was wrong, but that first PR is already merged so here we are) |
Add GHA to check for copyright update. Move core logic from update-copyright githook into check_update_copyright.sh so the logic is shared between the githook and GHA. Remove required-githooks watermark since it did not work in all scenarios and the GHA checks are more secure than client-side githooks. Combination of #15552, #15596, #15636, #15639 Skip-build: true Signed-off-by: Dalton Bohning <[email protected]>
Add GHA to check for copyright update. Move core logic from update-copyright githook into check_update_copyright.sh so the logic is shared between the githook and GHA. Remove required-githooks watermark since it did not work in all scenarios and the GHA checks are more secure than client-side githooks. Combination of #15552, #15596, #15636, #15639 Skip-build: true Signed-off-by: Dalton Bohning <[email protected]>
Add GHA to check for copyright update. Move core logic from update-copyright githook into check_update_copyright.sh so the logic is shared between the githook and GHA. Remove required-githooks watermark since it did not work in all scenarios and the GHA checks are more secure than client-side githooks. Combination of #15552, #15596, #15636, #15639 Skip-build: true Signed-off-by: Dalton Bohning <[email protected]>
Since it did not work in all scenarios and the GHA checks are more secure than client-side githooks.
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: