Skip to content

Conversation

@ceorourke
Copy link
Member

Follow up to #81020 (and a few others) to remove the AlertRuleExcludedProjects and AlertRuleTriggerExclusion models. There will be a final PR to fully remove them and then they're finally gone!

@ceorourke ceorourke requested a review from a team as a code owner November 25, 2024 20:13
@ceorourke ceorourke requested a review from a team November 25, 2024 20:13
@ceorourke ceorourke requested a review from a team as a code owner November 25, 2024 20:13
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Nov 25, 2024
@github-actions
Copy link
Contributor

This PR has a migration; here is the generated SQL for src/sentry/migrations/0796_rm_excluded_projects_triggers.py ()

--
-- Moved model AlertRuleExcludedProjects to pending deletion state
--
-- (no-op)
--
-- Moved model AlertRuleTriggerExclusion to pending deletion state
--
-- (no-op)

@codecov
Copy link

codecov bot commented Nov 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #81264      +/-   ##
==========================================
- Coverage   80.35%   80.35%   -0.01%     
==========================================
  Files        7221     7221              
  Lines      319612   319589      -23     
  Branches    20783    20783              
==========================================
- Hits       256821   256795      -26     
- Misses      62396    62399       +3     
  Partials      395      395              

@wedamija
Copy link
Member

Probably need to update snapshots and so on

@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Nov 25, 2024
@github-actions
Copy link
Contributor

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

@ceorourke ceorourke merged commit 2af89fa into master Nov 26, 2024
51 checks passed
@ceorourke ceorourke deleted the ceorourke/rm-excluded-projects branch November 26, 2024 17:56
andrewshie-sentry pushed a commit that referenced this pull request Dec 2, 2024
Follow up to #81020 (and a few
others) to remove the `AlertRuleExcludedProjects` and
`AlertRuleTriggerExclusion` models. There will be a final PR to fully
remove them and then they're finally gone!
@github-actions github-actions bot locked and limited conversation to collaborators Dec 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Scope: Backend Automatically applied to PRs that change backend components Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants