skills.rest
udecode
udecodeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

sync-main-to-next

Syncs origin/main into origin/next through release-lanes with dry-run, push, and verification steps.

16.5k|997|Updated Dec 2, 2019
Search Tags:#release management#Git#ci monitoring#branch sync#GitHub actions#npm dist-tags#beta lane
One-click install
npx skills add https://github.com/udecode/plate --skill sync-main-to-next
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-main-to-next
Source: https://github.com/udecode/plate/tree/main/.agents/skills/sync-main-to-next
Command: npx skills add https://github.com/udecode/plate --skill sync-main-to-next

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a stable release, the beta lane (next) falls behind main, and manually syncing branches, watching CI runs, and verifying npm dist-tags is repetitive and error-prone. This Skill provides a one-command shortcut that runs the direct main-to-next sync without the full release-lane ceremony.

Core Features & Use Cases

  • Direct Branch Sync: Runs the release-branch-prs script in dry-run, push, and verify modes to sync origin/main into origin/next.
  • Workflow Monitoring: Watches only the GitHub Actions release and CI runs triggered by the pushed sync commit.
  • Release Readback: Verifies npm dist-tags (latest and beta), GitHub releases, and cleans up stale sync PRs.
  • Use Case: After publishing a stable release of platejs, invoke the shortcut to fast-forward the beta lane, confirm the release and CI runs pass, and report npm tag status in a five-line handoff.

Quick Start

Ask the assistant to run sync-main-to-next to push the latest main into the next branch and verify the release.

Frequently Asked Questions about sync-main-to-next

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync the main branch into the next branch after a release?▼

Run the sync-main-to-next shortcut, which executes the release-branch-prs script in dry-run, push, and verify modes. It pushes a direct sync commit to next and then watches the resulting release and CI workflow runs.

What is the difference between sync-main-to-next and a main-to-next pull request?▼

This shortcut pushes the sync commit directly to next instead of opening a main-to-next PR. It is a convenience wrapper around the release-lanes sync lane, not a separate release system, and skips promotion and broad release ceremony.

Does this workflow handle promoting next back into main?▼

No. The shortcut explicitly does not touch promotion, which is the next-to-main direction owned by the full release-lanes process. It only performs the main-to-next catch-up sync.

When does the main-to-next sync stop and require manual intervention?▼

It stops on a dirty checkout rejected by the sync script, real source conflicts outside release metadata, branch protection rejecting the push, release or CI failure after one repair attempt, or npm and GitHub readback mismatches.

How do I verify the beta release after syncing main into next?▼

Check npm dist-tags with npm view platejs dist-tags, compare the latest and beta versions, list recent GitHub releases, and confirm no stale sync/main-to-next PRs remain open against next.

Related Skills

Explore More Software Engineering Skills→
elbrunoelbruno
2

release-process

Guide npm package and GitHub release publication with semver and token checks.

Community
Advanced
emmepraemmepra
1

release-train

Group dev PRs into a main release PR with CI and rollback checks.

Community
Advanced
dotnetdotnet
209

release-process

Standardizes npm and GitHub releases with semver validation and automation checks.

Official
Advanced
calebeynoncalebeynon

pr-merge

Merge pull requests with conflict resolution and worktree cleanup.

Community
Advanced