Enable configuration for no local hook or plugin failure behavours #2936
+223
−19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Currently if you block local hooks or plugins the build fails, however there are cases during migration where you may want to just print a warning for the developer while still not executing hooks or plugins.
Context
This change enables teams to block local hooks without breaking the build.
Changes
This change adds a couple of new flags which allow configuration of the failure behaviour to either "error" or "warn".
Testing
go test ./...). Buildkite employees may check this if the pipeline has run automatically.go fmt ./...)