Two new docs under docs/:
- upstream-prs.md — how to send a PR upstream using the
~/dev/upstream-prs/ worktree flow. Opens with a "Primer" section
for anyone new to forks / pull requests (the three remote roles —
upstream / github-fork / origin — explained as a table), then the
per-project prerequisites, the prb/prc helper-driven workflow, and
a "Common pitfalls" section.
- lnbits-upstream-flow.md — reference for how lnbits/lnbits actually
moves: the dev/main branch split, the squash-merge PR convention,
the non-FF release merge from dev into main, and how to read the
history with --first-parent. Adapted from internal aiolabs notes
with the fork-versioning specifics stripped; closing section is
generic guidance for anyone maintaining their own long-lived fork.
README links both from a new "Further reading" section. The prior
"Contributing" section is retitled "Contributing to this scaffold"
to avoid colliding with the new upstream-PR doc on the term.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
