Open
Conversation
Ensure all Flue issue triage comments identify the issue triage bot in the first sentence and keep the canned comments casually professional. Close duplicates of not planned canonical issues with the same not planned resolution, and allow the workflow to comment as the configured SentryIntern GitHub App via FLUE_CLIENT_ID and FLUE_PRIVATE_KEY. Co-Authored-By: GPT-5 Codex <noreply@openai.com>
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Move issue triage execution to the shared getsentry/.github workflow and keep this repository as a lightweight issue-opened caller. Remove the local Flue agent, skill, docs, scripts, and dependencies now that the implementation lives in the org automation repo. Co-Authored-By: GPT-5 Codex <noreply@openai.com>
dcramer
changed the title
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit a3f4bae. Configure here.
Remove the sentry-mcp issue triage workflow entirely now that the organization automation owns issue triage from the .github repository. Keep this PR focused on deleting local Flue implementation and dependencies from sentry-mcp. Co-Authored-By: GPT-5 Codex <noreply@openai.com>
dcramer
changed the title
Keep sentry-mcp subscribed to opened issue events with a tiny caller workflow while the Flue implementation lives in getsentry/.github. This preserves issue event delivery without carrying local Flue code or dependencies in this repository. Co-Authored-By: GPT-5 Codex <noreply@openai.com>
dcramer
changed the title
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
1 participant
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.
Subscribe sentry-mcp issue opens to the shared Flue triage workflow in
getsentry/.github. GitHub issue events are repository-scoped, so this repo still needs a tiny local workflow whose only job is to call the central reusable workflow.Shared Triage Caller
.github/workflows/issue-triage.ymlnow passes the opened issue number andgithub.repositoryintogetsentry/.github/.github/workflows/issue-triage.yml@mainwith inherited secrets. The shared workflow owns the Flue agent, repo allowlist, Sentry Intern app token, and issue-closing behavior.Local Flue Cleanup
Removes the sentry-mcp-local Flue agent, skill docs, helper scripts, Flue docs, and Flue-only package dependencies so this repo only carries the event subscription shim.
Depends on getsentry/.github#180.