fix(agreements): allowlist splunk-ta-helper bot - #75
Merged
mbruzda-splunk merged 1 commit intoSep 21, 2026
Merged
mbruzda-splunk merged 1 commit into
mbruzda-splunk merged 1 commit into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
mbruzda-splunk
force-pushed
the
fix/cla-allowlist-splunk-ta-helper
branch
from
2525c53 to
ed5aae8
Compare
September 11, 2026 14:15
mbruzda-splunk
enabled auto-merge
September 11, 2026 14:21
mkolasinski-splunk
approved these changes
Sep 21, 2026
Copy link
Copy Markdown
|
🎉 This PR is included in version 1.7.4 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sorry, something went wrong.
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
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.
The reusable CLA/COC workflow allowlist must use splunk-ta-helper[bot], matching the actual GitHub bot login. The fix(...) conventional commit will produce patch release v1.7.4 through semantic-release, and the update-semver job will advance the floating v1.7 alias so existing consumers need no migration.