Document allowlist automation workflows in README#714
Conversation
|
Better documents that we have in fact two different workflows. |
b090a1a to
0422f96
Compare
|
Rebased onto
No other content changes — the structure and section ordering are the same as before the rebase. |
|
Depends on #717 |
raboof
left a comment
There was a problem hiding this comment.
I like the text changes.
Splitting the mermaid graph into two graphs definitely makes these individual workflows easier to understand, but I'm not sure it makes "the whole system" easier to understand. I wonder if it'd make sense to have one "full" graph and then per section have that same graph but highlight the steps that are relevant for that workflow? OK as-is, too, though.
Addresses @raboof review feedback on #714: - Pull the `expires_at` + `remove_expired.yml` explanation out of the "Updating Version" section into its own "Automatic Expiration of Old Versions" subsection between "Manual Version Addition" and "Removing a Version Manually", with its own mini mermaid graph showing the daily cleanup edge that was previously a self-loop on the updating diagram. - Apply the line-288 wording suggestion: the manual-removal intro now says the manual path is needed only when you "can't wait for the entry to expire" rather than "the next daily run" — the daily cadence is a detail of the new section, not of the manual flow. Rebased onto current main; no content changes beyond the review feedback. Generated-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0422f96 to
c07be58
Compare
Address @raboof's review idea of "one full graph" that ties the per-section diagrams together. Adds a Pipeline Overview subsection at the top of the allow-list management section with a single mermaid graph covering every entry point (human PR, Dependabot PR, daily cron), every workflow (update_actions, update_composite_action, remove_expired, verify_dependabot_action, check_approved_limit) and the three files they keep in sync (actions.yml, approved_patterns.yml, for-dependabot-triggered-reviews/action.yml). Edge styling carries meaning: thick arrows are regeneration flows that rewrite the generated files, thin arrows feed new content into the pipeline, dotted arrows are observer workflows. Node colors separate the source of truth, generated files, triggers and observer workflows. The existing per-section diagrams remain as focused zooms into each slice of the overall flow. Generated-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
I also updated overall pipeline description. This one depends on merging #735 |
Summary
actions.yml,.github/workflows/dummy.yml, andapproved_patterns.ymlin sync (update_actions.yml,update_dummy.yml,remove_expired.yml,verify_dependabot_action.yml,check_approved_limit.yml)expires_at+ the dailyremove_expired.ymljob, leaving the manual removal section for urgent/security casesTest plan
.github/workflows/Generated-by: Claude Opus 4.6 (1M context)