Skip to main content

Draft the plan

1

Open the workbench in plan mode

2

Describe the goal

Say what the plan should produce and from what:
The plan drafter finds the tools for each part of the goal, writes the plan, checks it, and puts it in the pane:
The workbench after drafting: the goal and the plan drafter's summary on the left, and the release_notes_since_latest_release plan on the right with steps release, commits, a file_changes map over changed and row, notes, and the output, marked valid.

The drafted plan in the pane: the release, the commits since it, each commit's changed files, and one infer step that writes the notes.

3

Answer its questions

The drafter may ask for clarification on statuses or labels that it needs to draft the plan. Answer the questions in the form to continue.
The workbench's answer form over the chat, asking whether merge commits should get a release note (no) and whether to leave out commits that only change .github/, with a field for anything else the planner should know.

The drafter's questions, each filled in with its guess.

4

Rename it

The plan editor takes over once the draft is in the pane. Ask it for the identifier you want:
5

Save

Press Ctrl+S. graph writes the plan to ./.graph/plans/unreleased_changes.yaml.

Run the plan

Debug a plan

Step through a run in the workbench.

Plan file

Every field a plan file takes.

Create a tool in the workbench

Draft a tool the plan needs.