Feature/update docs v2#59
Open
csoceanu wants to merge 8 commits into
Open
Conversation
When forge.docs_repo Jira project property is set, the update_documentation node clones the separate docs repo, runs the update agent in a container with both repos mounted (code repo read-only, docs repo read-write), and creates a fork-based PR for the docs changes. Changes: - Add get_project_docs_repo() to JiraClient for reading the optional forge.docs_repo project property - Add extra_mounts parameter to ContainerRunner for mounting additional read-only volumes into containers - Expand docs_updater node with _update_separate_docs_repo() that handles clone, dual-mount container run, fork, push, and PR creation - Add update-docs-separate.md prompt template that tells the agent where both repos are mounted - Add docs_pr_url field to feature and bug workflow state - Improve update-docs skill: broader file discovery, -rlFi grep, two-pass evaluation, step 6 review beyond grep, always read README, skip auto-generated files, add new information from diff to existing docs Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Add "Documentation Update" step to workflow diagrams and tables - Add forge.docs_repo project property to config documentation Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Move separate docs repo logic from docs_updater.py into a dedicated update_docs_repo node that runs post-merge. When forge.docs_repo is set, clones both repos, runs the update agent with the code repo mounted read-only, and creates a fork-based PR for the docs changes. Wire into both workflows: - bug: post_merge_summary → update_docs_repo → END - feature: human_review_gate → update_docs_repo → complete_tasks Non-blocking — failures log a warning and proceed. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
# Conflicts: # src/forge/workflow/feature/graph.py
Update bug workflow guide, config reference, README, and workflow graph to reflect the new post-merge docs repo update step and the forge.docs_repo Jira project property. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds support for updating documentation that lives in a separate repository from the code. When the
forge.docs_repoJira project property is set, Forge automatically updates the docs repo after a code PR is merged.update_docs_repo— post-merge node that clones both repos, runs the update-docs skill with the code repo mounted read-only, and creates a fork-based PR for the docs changesforge.docs_repo— optional project property pointing to the docs repo (owner/repoformat)extra_mountsin ContainerRunner — allows mounting additional read-only volumes into containerspost_merge_summary → update_docs_repo → END, feature:human_review_gate → update_docs_repo → complete_tasksforge.docs_repois not set or the update fails, the workflow proceeds normally-rlFi), two-pass evaluation, "review beyond grep" step, skip auto-generated filesHow it works
update_docs_repochecksforge.docs_repovia Jira project properties/workspace= docs,/code-repo= code read-only)Test plan