Add rule to enforce Opsgenie casing#96
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
janine-c
approved these changes
Jun 25, 2026
janine-c
left a comment
janine-c
left a comment
Contributor
There was a problem hiding this comment.
Thanks for this! I tested locally on your branch and it looks like it's working perfectly ✨
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
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.
Summary
words_case_sensitive.ymlto flag incorrect casing of Opsgenie (e.g.OpsGenie,opsgenie) and suggest the correct formOpsGenieentry inheadings.ymlto match the correctOpsgeniecasingTest plan
OpsGenieand suggestsOpsgenieopsgenieand suggestsOpsgenieOpsgeniepasses without a warning🤖 Generated with Claude Code