update-docs

To keep MkDocs documentation in sync, review code changes on your feature branch against the main branch to identify necessary updates for guides, API reference pages, and example galleries based on new modules or modified APIs.

The best way to update Python project documentation is to map code modifications to specific documentation sections, guiding you on which Markdown files in the docs directory need updates to accurately explain the new functionality and usage.

Yes, you need local Git repository access to compare current branch changes against the main branch, pinpoint code modifications, and determine which documentation sections require corresponding updates.

You can verify updated MkDocs documentation by running local build commands provided during the review process, which check for errors and ensure your guides and API references compile correctly after modifications.

You should update API reference pages when code changes introduce new modules, features, or API modifications, ensuring that the technical documentation accurately reflects the current state of the codebase.