Module overview
From finding to merged fix: a proposal you read, a yes you give, and a pull request you merge.
Owners who want fixes shipped without handing over the keys.
Why this module is important
- Understand the full path: audit, proposal, approval, pull request.
- Know that permission is granted per proposal and scoped to exact files.
- Merge on your schedule. Navlio never touches the default branch.
Recommended workflow
- 01
Ask for an audit of the connected repository.
- 02
Ask the agent to propose a fix. It drafts the exact edits and summarizes them.
- 03
Say yes when the proposal reads right. Navlio grants itself nothing beyond that proposal.
- 04
Review the pull request on GitHub and merge when you are ready. Nothing goes live until you merge it.
Four rails under every fix
Each step narrows what the next step is allowed to do.
The agent drafts the exact edits and shows you a summary. Nothing touches the repository at this point.
Your yes grants one permission limited to the exact files in the proposal, in pull request mode only.
Edits apply against the exact commit that was audited. If the repository moved, the fix fails instead of guessing.
Changes arrive on a navlio branch as a pull request. Nothing goes live until you merge it.
Important boundaries
Proposals are drafted server side from the stored audit. The conversation cannot smuggle content into a fix.
Permissions are scoped to the exact files of one proposal, in pull request mode only.
Edits apply against the audited commit. If the repository moved, the fix fails instead of guessing.
You can close the pull request and nothing happened.