Add: ChamberVerification Hook #539
Merged
Conversation
This file contains hidden or 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
Merged
Contributor
Author
|
@sds Rebased. Thank you. :) |
Owner
|
Hey @jfelchner, looks like you accidentally removed some configuration from another (unrelated) PR. Can you rebase again? Thanks! |
When working with [settings verification](Verifying-Settings), it's important to remember to let the Approver know that settings have changed and that the current file signature will no longer match. You can enable it by creating an `.overcommit.yml` file and adding: ```yaml ChamberVerification: enabled: true ``` Whenever you commit any of your settings files, the hook will warn the user that the signature no longer matches and that the Approver needs to be notified. If you'd like to specify the name and email address of the Approver, you can add that to the configuration: ```yaml ChamberVerification: enabled: true approver_name: "Jeff Felchner" approver_email: "jeff@example.com" ```
Contributor
Author
|
Ahhhhhhh!!!! Sorry man. Should be good now. |
Contributor
Author
|
@sds any chance we can get a release out soon? 😁 |
Owner
|
0.42.0 was just released! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When working with settings verification, it's
important to remember to let the Approver know that settings have
changed and that the current file signature will no longer match.
You can enable it by creating an
.overcommit.ymlfile and adding:Whenever you commit any of your settings files, the hook will warn the
user that the signature no longer matches and that the Approver needs to
be notified.
If you'd like to specify the name and email address of the Approver, you
can add that to the configuration: