From 5f0a9fcdecf5e7b53d1a6c82a31e7275fbcb19ac Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Fri, 2 Oct 2026 05:41:24 +0000 Subject: [PATCH] Fix broken gh-aw reference links in cost-tracker docs The links used the wrong domain (github.github.com instead of github.github.io) and pointed to nonexistent paths (reference/token-usage/, reference/firewall/). Replaced with the correct, working URLs: - https://github.github.io/gh-aw/reference/artifacts/#firewall-audit-logs - https://github.github.io/gh-aw/reference/network/ Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- docs/cost-tracker.md | 4 ++-- workflows/cost-tracker.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/cost-tracker.md b/docs/cost-tracker.md index 28d58ef..b13467e 100644 --- a/docs/cost-tracker.md +++ b/docs/cost-tracker.md @@ -72,8 +72,8 @@ already there if you are running gh-aw with firewall enabled (the default). ## Learn More -- [token-usage.jsonl reference](https://github.github.com/gh-aw/reference/token-usage/) -- [gh-aw firewall documentation](https://github.github.com/gh-aw/reference/firewall/) +- [token-usage.jsonl reference](https://github.github.io/gh-aw/reference/artifacts/#firewall-audit-logs) +- [gh-aw firewall documentation](https://github.github.io/gh-aw/reference/network/) - [CI Doctor workflow](ci-doctor.md) — investigate CI failures automatically ## Going Further diff --git a/workflows/cost-tracker.md b/workflows/cost-tracker.md index c906f69..e3179dd 100644 --- a/workflows/cost-tracker.md +++ b/workflows/cost-tracker.md @@ -145,7 +145,7 @@ Build a report using this template. Fill in `$TOTAL_COST` and the breakdown tabl -*Data from [token-usage.jsonl](https://github.github.com/gh-aw/reference/token-usage/) written by gh-aw's firewall.* +*Data from [token-usage.jsonl](https://github.github.io/gh-aw/reference/artifacts/#firewall-audit-logs) written by gh-aw's firewall.* ``` **If a PR number was found**: post this as a comment on that PR using the `add_comment`