How Autopilot keeps documentation current
Autopilot connects a documentation Space to repository changes and prepares suggested documentation updates. It helps maintain an existing documentation set after the initial generation.
The workflow
- A configured repository event arrives for an enabled Space link.
- DocuWriter checks the changed code and relevant documentation.
- Suggestions appear for review when an update is warranted.
- A permitted user applies, discards or snoozes the suggestions. Optional auto-apply can handle eligible changes when configured.
A suggestion may update an existing page or propose a new page. A received code event does not guarantee a suggestion: some changes have no relevant documentation impact or are filtered out.
Before enabling it
Start with a useful Space and a working provider connection. Choose the repository, branch and scope that correspond to the documentation. A Space can have multiple repository links, which is useful when one system spans repositories.
Set up Autopilot and begin with manual review so you can assess the relevance and accuracy of suggestions.
Access and usage
Preview access and permission to apply changes are separate. The app shows which actions your account or team can use. Generated suggestions can consume credits on entitled paid workflows; applying a suggestion is not a new documentation generation.
A one-time ZIP cannot receive provider events. Use a Git connection when you need ongoing maintenance.
Use Update Documentation Gaps for deliberate broad expansions; use Autopilot for changes prompted by repository activity.
Updated