Repository navigation
ci: notify Grok Bot when an issue is opened - #4112
Closed
caio-pizzol wants to merge 1 commit into
Closed
caio-pizzol wants to merge 1 commit into
caio-pizzol wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Sends each newly opened issue to a Grok Bot routine, which starts an investigation thread and pings Caio. The bot never writes to GitHub.
Why an Action: Grok Bot's GitHub triggers have no `issue opened` event, and its webhook needs an `Authorization: Bearer` header that a repository webhook can't send.
Tested the step locally against a mock endpoint: it sent the bearer header and the JSON body, and it skipped with exit 0 when the secrets were empty.
🤖 Generated with Claude Code