Ensure refund creates an associated supporter activity record - #1245
Draft
wwahammy wants to merge 9 commits into
Draft
Conversation
wwahammy
force-pushed
the
4572-ensure-refund-creates-supporter-activity-record
branch
from
July 14, 2025 17:03
f4f47d1 to
83a3be7
Compare
wwahammy
changed the base branch from
supporter_level_goal
to
add-requirements-to-refund-and-activities
July 14, 2025 20:31
…sure-refund-creates-supporter-activity-record
…sure-refund-creates-supporter-activity-record
…sure-refund-creates-supporter-activity-record
…sure-refund-creates-supporter-activity-record
…sure-refund-creates-supporter-activity-record
…sure-refund-creates-supporter-activity-record
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.
InsertActivity.refundsto accept paymentsInsertActivity.for_refundsis being passedPaymentsNOTE: DO NOT discuss internal CommitChange information in your PR; this PR will be public.
Link back to the issue in the Tix repo when you need to do that.