Repository navigation
Manual steps: push notifications are merged - #16
Merged
Merged
Conversation
Step 7 still said PR #12 wasn't on main. Push notifications are merged and ship with the next successful deploy; 0003_push and 0004_protected_superadmin touch different tables, so their arrival order doesn't matter. The test-user expiry plan already reserves 0005. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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
Follow-up to #12 and #15 landing on
main:remaining_manual_steps.mdstep 7 said push notifications weren't merged; they are, and ship with the next successful deploy (which applies0003_push.sql).main:0003_push,0004_protected_superadmin(independent tables, so arrival order doesn't matter), and the unbuilt test-user expiry reserves0005inplan-remaining.md.Test plan
🤖 Generated with Claude Code