What problem does it solve?
Docs commits merged to master in the nx repo do not automatically reach the branches that deploy nx.dev. This Skill syncs those commits onto both the live website branch and the current release branch, preventing the release pipeline from silently wiping out published documentation updates.
Core Features & Use Cases
- Dual-branch sync: Cherry-picks
docs( and feat(nx-dev) commits onto both website-<major> and the matching <major>.<minor>.x release branch.
- Automatic branch detection: Identifies the highest website branch and its matching release branch using git ref queries.
- Safe failure handling: Aborts conflicting cherry-picks, skips already-applied commits, and reports per-branch results without pushing.
- Use Case: After several docs PRs merge to master, ask the assistant to update the docs website; it computes the delta since the last sync, cherry-picks the commits onto
website-23 and 23.1.x, and reports which commits succeeded, were skipped, or failed.
Quick Start
Ask the assistant to update the docs website by cherry-picking the latest docs commits from master onto the website and release branches.