Repository navigation
Regenerate the documentation graphs on pull requests - #318
Merged
Merged
Conversation
Runs both graph generators on pull requests that change app/ or the generator scripts, and commits the SVGs to the pull request's branch if they changed. Pull requests from forks are skipped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2 tasks done
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
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.
Stacked on the criteria and process graph images PR (base
docs/criteria-graph-images).Summary
Adds
.github/workflows/doc-graphs.yml. On pull requests that changeapp/**, either generator script or the workflow itself, it installs graphviz and Node, runsscripts.generate_criteria_graphsandscripts.generate_process_graphs, and pushes a "Regenerate the documentation graphs" commit to the pull request's branch if any SVG changed.Notes
GITHUB_TOKENdon't trigger other workflows, so Test and Lint doesn't re-run on the bot's commit (and the workflow can't trigger itself). Themainruleset doesn't require status checks, so merging isn't blocked.mainruleset requires a pull request with no bypass, and the shared deploy workflow builds the commit the run started from.🤖 Generated with Claude Code