Skip to content

Replace ineffective follow_own_posts migration with a working one#2005

Merged
Oaphi merged 1 commit intodevelopfrom
trichoplax/replace_ineffective_follow_own_posts_migration
Mar 4, 2026
Merged

Replace ineffective follow_own_posts migration with a working one#2005
Oaphi merged 1 commit intodevelopfrom
trichoplax/replace_ineffective_follow_own_posts_migration

Conversation

@trichoplax
Copy link
Contributor

This deletes the migration db/migrate/20260208223211_follow_own_posts.rb and adds a new migration db/migrate/20260304104100_follow_own_posts.rb that uses unscoped Post to make the post author a follower of new threads for every post.

@codecov
Copy link

codecov bot commented Mar 4, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.74%. Comparing base (38c6dc0) to head (8e2b8ae).
⚠️ Report is 2 commits behind head on develop.

Additional details and impacted files
Components Coverage Δ
controllers 75.85% <ø> (+0.03%) ⬆️
helpers 85.08% <ø> (ø)
jobs 66.88% <ø> (ø)
models 93.01% <ø> (ø)
tasks 61.11% <ø> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@trichoplax trichoplax requested a review from a team March 4, 2026 11:04
@Oaphi Oaphi merged commit f8f56f5 into develop Mar 4, 2026
18 of 20 checks passed
@Oaphi Oaphi deleted the trichoplax/replace_ineffective_follow_own_posts_migration branch March 4, 2026 11:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants