Tooling · rule
cli.approval_arguments
A jadpo approval command is given an argument it doesn't take, names a --before git doesn't know, or has nothing to compare with.
Area 14, Tooling; not declinable; the next step is usually the agent's.
Why Jadpo refuses it
The approval report is the difference between this change and its before side, the default branch at its merge base. jadpo approval reports on the whole project, so it takes no path or name, and with no before side there is no difference to report.
What it looks like
A word is given after the command:
jadpo approval lending error jadpo approval takes no arguments
- reason
- It was given
lending. - next
- Run
jadpo approval(agent) - rule
- cli.
approval_ arguments - help
- https://jadpo.
dev/docs/errors/cli. approval_ arguments
(agent) at the end of the next: line means your coding agent can make the fix itself.
A project git doesn't hold has nothing to compare with:
jadpo approvalerror Nothing to compare with: not a git repository
- reason
- The approval report is the difference between this change and its before side, the default branch at its merge base, and there is none.
- next
- Commit the project to git with a default branch, or name a base with
--before <branch or commit>(agent) - rule
- cli.
approval_ arguments - help
- https://jadpo.
dev/docs/errors/cli. approval_ arguments
How to fix it
If you meant to explain this branch's change, run it with nothing after it, in a project committed to git:
jadpo approvalIt writes build/review/approval.md and .json, comparing with the default branch at its merge base.
If you meant to compare with something else, such as the commit a deployed build's events carry, name it:
jadpo approval --before 8d113e6It writes the same report, comparing with that commit.
Related
Markdown for agents: /docs/errors/cli.approval_arguments.md.Built from Jadpo main at e00e61f.