Publish a flow

The community flows are not a folder in this repository and need no pull request. Any public GitHub repository with the topic cornercase-flow is listed.

Publish yours

1. Export the flow you made: cornercase flow export 'My flow' > flow.toml.
2. Put it in a public repository, as flow.toml at the root (or cornercase-flow.toml). The repository’s description and topics are shown next to it; a description in the flow is shown first.
3. Add the topic cornercase-flow to the repository (the gear next to About).
4. Wait for the next refresh, scheduled every hour. The page lists the repository, its stars and the flow, and people import it with cornercase flow import you/your-repo.

Try the file first with the cornercase you have: cornercase flow import ./flow.toml --name test, then cornercase flow list shows the flow with anything that stops it from running.

What gets listed

A script reads the repositories with the topic on an hourly schedule, most starred first, and skips with a log line any that:

• has neither flow.toml nor cornercase-flow.toml at its root, is a fork, or is archived;
• has a file over 256 KiB or one cornercase cannot read, with no roles, an unknown agent, a role that is in no stage or a loop that goes back to a stage that does not exist;
• sets env or args in any role: a flow in the list may not;
• is made by a newer cornercase (version above 2), gives a role a worktree other than shared or own, gives the orchestrator a worktree of its own, has a role with worktree = "own" in a file that does not say version = 2, or runs two roles that edit the shared worktree side by side in one stage.

The list shows the flow as it was at the last refresh. Importing reads the repository’s current file, so what a reader imports can be newer than what the page showed; keep prompts honest, and a reader will not be surprised.

Trust

Caution

Nobody reviews the flows in the list, and their agents never ask for permission. Whoever imports a flow is responsible for what it does, so write prompts that say plainly what they do, and never put secrets, tokens or machine-specific paths in one.

See Trust and security for what readers are told.