update-docs-on-code-change

To update documentation after code changes, trigger an automated sync workflow that refreshes file headers, docstrings, and Markdown docs to match the latest code edits. It applies diffs and awaits your confirmation before applying final updates.

Yes, you can synchronize Python docstrings and Markdown docs together. The workflow maps source code edits to related Markdown files, ensuring architectural descriptions and headers remain accurate across Python, IPYNB, and MQL4 sources.

Keeping code headers and architecture docs in sync is best handled by an automated validation workflow triggered after code edits. It updates related descriptions, validates completeness, and shows diffs before applying any changes.

Yes, this documentation sync workflow supports IPYNB and MQL4 files. It processes Python, MQL4, IPYNB, and Markdown sources to align headers and docstrings with recent code modifications.

To handle oversized Markdown documentation files, the sync workflow validates documentation completeness and proposes splitting large files into smaller ones. It enforces this update while awaiting your confirmation before changes are applied.

Documentation validation fails after editing code signatures because headers and docstrings are no longer aligned with the new behavior. Running a docs sync refreshes all related documentation and validates completeness before finalizing updates.