docs: document stripe branch and add propagate/CI support - #229
Merged
Conversation
Point main docs and README at the optional stripe branch, document the merge recipe and conflict-prone files, and extend propagate.yml and test.yml so stripe receives main updates and runs CI with dummy Stripe env. Co-authored-by: Cursor <cursoragent@cursor.com>
Narrowing push to main/stripe would drop CI on feature branches and modal/hetzner; only extend pull_request targets for stripe.
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
2 participants
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
stripebranch in README, overview, customization, deployment, and contributing guides (pointers only — no billing code or07-billing.qmdonmain)stripetopropagate.ymlmatrix with automaticpyproject.toml/uv.lockoverlay resolution (mirrors Modal)test.ymlto run onstripepushes/PRs with dummy Stripe env vars (harmless onmain)Context
Billing lands on the dedicated
stripebranch (notmain). This PR wires up propagation and fork documentation so core template changes onmainflow tostripeautomatically.Closes #228
Test plan
main— no billing code, dummy Stripe env is inert)mainpush propagates tostripevia updated workflowgreat-docs buildoptional)Made with Cursor