docs: document how Capacitor+ fixes flow back to ionic-team/capacitor

Merged
RI
10d ago
+57-0

What

  • Add a Fixes flow back upstream section to README.md near the other top-level Capacitor+ feature sections.
  • Document fork-only landing on plus, manual upstream PRs on ionic-team/capacitor main, and how status is tracked today (including what does not exist).

Why

  • Website and contributor docs need an accurate, citeable description of the fork → upstream path, separate from the daily upstream → fork sync.

How

  • Investigated workflows (ci.yml, bump_version.yml, build.yml, sync-upstream.yml, sync-branches.yml), labels, and real upstream PRs (#8284, #8203, riderx authorship filter).
  • Described only observed behavior; called out the absence of UPSTREAM.md and backport labels.
  • Verified README.md has no en/em dashes (rg).

Testing

  • rg -n '[\u2013\u2014]' README.md (no matches)

Not Tested

  • n/a (docs only)

Docs PR: https://github.com/Cap-go/website/pull/1395 (page /docs/plugins/capacitor-plus/upstream-backports/)

Open in Web Open in Cursor 

Autofix with [code]smith
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.

Summary by CodeRabbit

  • Documentation
    • Added guidance on the fork-to-upstream fixes process, including fork-only pull requests, review, patch-version tagging, and npm staging and approval.
    • Clarified that matching upstream pull requests are opened manually, targeting main for standard fixes or next for breaking changes.
    • Documented the separate inbound sync workflow, including its limits, exclusions, dispatch requirements, conflict handling, and recovery steps.
    • Added upstream pull request examples and details on tracking signals for inbound and backport pull requests.