Skip to content

feat(triage signals): Seer orgs on new pricing need to have Github integration to use autofix #104477

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
Mihir-Mavalankar wants to merge 2 commits into
base: master
Choose a base branch
from
Open

feat(triage signals): Seer orgs on new pricing need to have Github integration to use autofix #104477

Mihir-Mavalankar wants to merge 2 commits into from
+28 −3

Conversation

@Mihir-Mavalankar
Copy link
Contributor

@Mihir-Mavalankar Mihir-Mavalankar commented Dec 5, 2025 •
edited
Loading

PR Details

@Mihir-Mavalankar Mihir-Mavalankar self-assigned this Dec 5, 2025
@Mihir-Mavalankar Mihir-Mavalankar requested review from a team as code owners December 5, 2025 21:14
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Dec 5, 2025
@Mihir-Mavalankar
Copy link
Contributor Author

Mihir-Mavalankar commented Dec 5, 2025

@roaga I'm unsure if this is the right way to stop it in the UI. lmk what you think.

@getsentry getsentry deleted a comment from codecov bot Dec 5, 2025
roaga
roaga reviewed Dec 5, 2025
View reviewed changes
Copy link
Member

@roaga roaga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i don't think we're requiring code mappings, only github integration

@Mihir-Mavalankar Mihir-Mavalankar changed the title feat(triage signals): Seer orgs on new pring need to have Github integration to use autofix feat(triage signals): Seer orgs on new pricing need to have Github integration to use autofix Dec 6, 2025
@Mihir-Mavalankar
Copy link
Contributor Author

Mihir-Mavalankar commented Dec 6, 2025

i don't think we're requiring code mappings, only github integration

Okay so that is already checked in the issue details UI right? So i can leave that unchanged.

And in kickoff_seer_automation should I just use get_autofix_integration_setup_problems just to check that the project has github integration?

@Mihir-Mavalankar
Copy link
Contributor Author

Mihir-Mavalankar commented Dec 6, 2025 •
edited
Loading

Actually get_autofix_integration_setup_problems checks the org level integration not project level so I can't use that. The org could have the integration but that specific project might not.
Code mapping might be best for project level. Is there any catch/drawback with them?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@roaga roaga Awaiting requested review from roaga

At least 1 approving review is required to merge this pull request.

Assignees

@Mihir-Mavalankar Mihir-Mavalankar

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@Mihir-Mavalankar @roaga