Repository navigation
Expand audit-workflows repo memory taxonomy - #32253
Merged
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Expand audit-workflows repo memory with more data categories
Expand audit-workflows repo memory taxonomy
May 15, 2026
pelikhan
marked this pull request as ready for review
May 15, 2026 02:39
Contributor
There was a problem hiding this comment.
Pull request overview
Expands the audit-workflows repo-memory contract so audits can persist richer cross-run artifacts (history, trends, known issues, recommendations, anomalies, and summary metrics) and adds a unit test to guard the terminology + taxonomy.
Changes:
- Updated
audit-workflows.mdto replace “Cache Memory” with “Repo Memory” and define the expanded persisted files + cross-run correlation rules. - Added a Go unit test that validates the workflow source contains the new terminology and expected repo-memory guidance.
- Regenerated
chaos-pr-bundle-fuzzer.lock.ymlwith substantial compiled workflow updates (versions/structure).
Show a summary per file
| File | Description |
|---|---|
| pkg/workflow/audit_workflows_repo_memory_test.go | Adds a unit test to assert the workflow source includes updated repo-memory terminology and guidance snippets. |
| .github/workflows/audit-workflows.md | Updates the workflow source documentation to the expanded repo-memory taxonomy and cross-run merge/ID rules. |
| .github/workflows/chaos-pr-bundle-fuzzer.lock.yml | Large regenerated lock workflow update included in the PR. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 3/3 changed files
- Comments generated: 3
Comment on lines
+19
to
+29
| expectedSnippets := []string{ | ||
| "Repo Memory", | ||
| "workflow-trends.json", | ||
| "known-issues.json", | ||
| "recommendations.json", | ||
| "anomalies.json", | ||
| "metrics-summary.json", | ||
| "stable IDs", | ||
| "recurrence and persistence counters", | ||
| "cross-referenced across days", | ||
| } |
Comment on lines
+83
to
+95
| **Repo Memory**: Store findings in `/tmp/gh-aw/repo-memory/default/`: | ||
| - `audit-history.jsonl` — append one structured summary entry per audit cycle | ||
| - `workflow-trends.json` — rolling per-workflow cost, duration, success, and reliability trends | ||
| - `known-issues.json` — recurring problems with first-seen, last-seen, recurrence count, affected workflows, and status | ||
| - `recommendations.json` — accumulated recommendations linked back to audits, workflows, and known issues | ||
| - `anomalies.json` — unusual runs or cost spikes with a multi-day persistence score and current escalation state | ||
| - `metrics-summary.json` — aggregate daily metrics used for charts and rollups | ||
|
|
||
| When updating repo memory: | ||
| - merge with existing data instead of overwriting useful history | ||
| - keep stable IDs so issues, recommendations, and anomalies can be cross-referenced across days | ||
| - increment recurrence and persistence counters when the same problem reappears | ||
| - compare the current audit with prior entries before deciding whether something is new or ongoing |
Comment on lines
+1
to
5
| # gh-aw-metadata: {"schema_version":"v3","frontmatter_hash":"9d38786c3da496eccc7458998312f258e4ccda832c19c066e99cd592fb7d1425","strict":true,"agent_id":"copilot"} | ||
| # gh-aw-manifest: {"version":1,"secrets":["COPILOT_GITHUB_TOKEN","GH_AW_CI_TRIGGER_TOKEN","GH_AW_GITHUB_MCP_SERVER_TOKEN","GH_AW_GITHUB_TOKEN","GH_AW_OTEL_GRAFANA_ENDPOINT","GH_AW_OTEL_GRAFANA_HEADERS","GH_AW_OTEL_SENTRY_ENDPOINT","GH_AW_OTEL_SENTRY_HEADERS","GITHUB_TOKEN"],"actions":[{"repo":"actions/cache/restore","sha":"27d5ce7f107fe9357f9df03efb73ab90386fccae","version":"v5.0.5"},{"repo":"actions/cache/save","sha":"27d5ce7f107fe9357f9df03efb73ab90386fccae","version":"v5.0.5"},{"repo":"actions/checkout","sha":"de0fac2e4500dabe0009e67214ff5f5447ce83dd","version":"v6.0.2"},{"repo":"actions/download-artifact","sha":"3e5f45b2cfb9172054b4087a40e8e0b5a5461e7c","version":"v8.0.1"},{"repo":"actions/github-script","sha":"3a2844b7e9c422d3c10d287c895573f7108da1b3","version":"v9.0.0"},{"repo":"actions/setup-node","sha":"48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e","version":"v6.4.0"},{"repo":"actions/upload-artifact","sha":"043fb46d1a93c77aae656e7c1c64a875d1fc6a0a","version":"v7.0.1"}],"containers":[{"image":"ghcr.io/github/gh-aw-firewall/agent:0.25.46"},{"image":"ghcr.io/github/gh-aw-firewall/api-proxy:0.25.46"},{"image":"ghcr.io/github/gh-aw-firewall/squid:0.25.46"},{"image":"ghcr.io/github/gh-aw-mcpg:v0.3.9","digest":"sha256:64828b42a4482f58fab16509d7f8f495a6d97c972a98a68aff20543531ac0388","pinned_image":"ghcr.io/github/gh-aw-mcpg:v0.3.9@sha256:64828b42a4482f58fab16509d7f8f495a6d97c972a98a68aff20543531ac0388"},{"image":"ghcr.io/github/github-mcp-server:v1.0.3","digest":"sha256:2ac27ef03461ef2b877031b838a7d1fd7f12b12d4ace7796d8cad91446d55959","pinned_image":"ghcr.io/github/github-mcp-server:v1.0.3@sha256:2ac27ef03461ef2b877031b838a7d1fd7f12b12d4ace7796d8cad91446d55959"},{"image":"node:lts-alpine","digest":"sha256:d1b3b4da11eefd5941e7f0b9cf17783fc99d9c6fc34884a665f40a06dbdfc94f","pinned_image":"node:lts-alpine@sha256:d1b3b4da11eefd5941e7f0b9cf17783fc99d9c6fc34884a665f40a06dbdfc94f"}]} | ||
| # ___ _ _ | ||
| # / _ \ | | (_) | ||
| # | |_| | __ _ ___ _ __ | |_ _ ___ |
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.
✨ Enhancement
What does this improve?
audit-workflowswas only instructed to persist a narrow set of audit artifacts, which limited multi-day trend analysis and caused recurring issues to be rediscovered instead of tracked. This expands the workflow’s repo-memory contract so audits can accumulate per-workflow trends, known issues, recommendations, anomalies, and rollup metrics across runs.Why is this valuable?
The workflow can now build durable memory around reliability/cost trends, cross-reference recommendations against prior audits, and assign persistence to repeated anomalies instead of treating each day as an isolated snapshot.
Implementation approach:
Workflow memory model
audit-history.jsonlworkflow-trends.jsonknown-issues.jsonrecommendations.jsonanomalies.jsonmetrics-summary.jsonCross-run correlation rules
Prompt terminology cleanup
Coverage