Record workshop creation and invitation batch sends - #2854
Draft
mroderick wants to merge 2 commits into
Draft
Conversation
This was referenced Sep 8, 2026
mroderick
force-pushed
the
feat/activity-workshops
branch
from
September 9, 2026 09:56
f5b0286 to
ee7782d
Compare
mroderick
force-pushed
the
feat/activity-workshops
branch
from
September 9, 2026 10:11
ee7782d to
47dec5f
Compare
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.
Summary
Fifth of the activity-log stack (base: #2853). Records organiser creation work:
workshop.createdwith aworkshops.created_by_idstamp (migration +belongs_to :created_by), andinvitation.send_batchfor the InvitationLogger initiator.Key changes
@workshop.created_by = current_userbefore save — atomic, noupdate_column, no validation-skipping disables.on_delete: :nullify), and a separatedisable_ddl_transaction!migration for the concurrently-built index, so a failed index build cannot strand a half-applied migration.created_by_idNULL (unknown); no backfill.Review notes
The concurrent index is precautionary at current table size. Post-deploy check:
SELECT COUNT(*) FROM workshops WHERE created_by_id IS NULL AND created_at > :deploy_time;should stay at 0.Stack: PR 6 adds the admin activity strip UI.
Context and motivation: #2857