pplaybookacademy/merge-canaryv1.0.1Public
Merge canary
Will your feature branch still work after merging latest main? Creates a temporary merge, checks for conflicts, and classifies the result as GREEN, TEXT_CONFLICT, SEMANTIC_CONFLICT, BRANCH_ALREADY_RED, or INDETERMINATE. Never modifies your current checkout. Read-only, no credentials.
Before you run it2 local tools
Everything here is checked on your machine when rote inspects the play. This page never learns what you have installed or which credentials you hold.
- ○gitlocal tool
Requires >=2.0. Run rote play inspect to check your host; unverified versions remain unknown.
- ○python3local tool
Requires >=3.10. Run rote play inspect to check your host; unverified versions remain unknown.
Inputs2, all optional
rote asks for these before running and shows the defaults it will use.
- Repo path
repo_pathPath to the git repository
optionalstringdefault.example.custom value allowed - Base branch
base_branchBase branch to merge into (e.g. main, master)
optionalstringdefaultmainexamplemaincustom value allowed
What it changes
No write operations are declared in this version's manifest.
Credentials remain in the recipient's local rote vault; this page and the publisher never receive them.
Runtime details
- rote CLIversion 0.62.0 or newer
- Servicesnone declared
- Digest
sha256:b2816a64a69a6886d4284876256e6395c695b60b72eef50a94cf3fb14494c565 - Archive size5712 bytes
- Published2026-09-04T09:10:11.992487+00:00
- Published withrote 0.76.0
Credential values and current readiness remain local. Opening this page never prompts for a credential, opens an authorization browser, or calls a service this play uses.
A play is a published, versioned automation package that runs on your own machine through rote, a free command-line tool. Opening this page installs nothing and runs nothing.