Renamed WelcomeEmailAutomation model to Automation#27658
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
WalkthroughRenames the database table 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
It looks like this PR contains a migration 👀 General requirements
Schema changes
Data changes
|
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #27658 +/- ##
==========================================
- Coverage 73.78% 73.77% -0.01%
==========================================
Files 1522 1522
Lines 128637 128637
Branches 15415 15413 -2
==========================================
- Hits 94911 94903 -8
- Misses 32792 32800 +8
Partials 934 934
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
98f8bd5 to
3cf186d
Compare
3cf186d to
bfdd26e
Compare
bfdd26e to
9ec10d0
Compare
towards https://linear.app/ghost/issue/NY-1260 This change should have no user impact. This renames "welcome email automation" to "automation" across the codebase. It does *not* rename any other models, so `WelcomeEmailAutomatedEmail` and `WelcomeEmailAutomationRun` still exist. This should be safe because we take sites offline for migrations.
9ec10d0 to
9d015f8
Compare
troyciesco
left a comment
There was a problem hiding this comment.
one quick question, and also we'll have to move the migration to 6.40 and fix the merge conflicts
| welcome_email_automated_emails: { | ||
| id: {type: 'string', maxlength: 24, nullable: false, primary: true}, | ||
| welcome_email_automation_id: {type: 'string', maxlength: 24, nullable: false, references: 'welcome_email_automations.id', constraintName: 'weae_automation_id_foreign', cascadeDelete: true}, | ||
| welcome_email_automation_id: {type: 'string', maxlength: 24, nullable: false, references: 'automations.id', constraintName: 'weae_automation_id_foreign', cascadeDelete: true}, |
There was a problem hiding this comment.
i'm guessing we'd change this column name to automation_id when we go about renaming this table? (same with runs)
There was a problem hiding this comment.
Yes, I plan to do that in a followup (see NY-1293).
closes https://linear.app/ghost/issue/NY-1282
This change should have no user impact.
This renames "welcome email automation" to "automation" across the codebase. It does not rename any other models, so
WelcomeEmailAutomatedEmailandWelcomeEmailAutomationRunstill exist.This should be safe because we take sites offline for migrations.