Skip to content

fix: prevent tool denial failures in daily-agent-of-the-day-blog-writer #43070

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 3 commits into from
Jul 3, 2026
Merged

fix: prevent tool denial failures in daily-agent-of-the-day-blog-writer #43070

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
216028f
Initial plan
Copilot Jul 3, 2026
20aaf29
fix: prevent tool denial failures in daily-agent-of-the-day-blog-writer
Copilot Jul 3, 2026
1b5cd85
revert: remove unrelated agentic-auto-upgrade.yml cron change
Copilot Jul 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions .github/workflows/daily-agent-of-the-day-blog-writer.lock.yml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

11 changes: 7 additions & 4 deletions .github/workflows/daily-agent-of-the-day-blog-writer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,8 @@ tools:
- "sed *"
- "find *"
- "echo *"
- "wc *"
- "expr *"
github:
mode: gh-proxy
lockdown: false
Expand Down Expand Up @@ -96,8 +98,9 @@ You write one short blog entry per weekday for the `gh-aw` docs blog spotlightin
- Use `agentic-workflows` `logs` and `audit` results as live evidence and include links to referenced issues/PRs.
- If a chart image is available, include it in the post.
- The `create_pull_request` patch must contain only text changes under `docs/src/content/docs/**`; never include binary assets in the PR patch — use `upload-asset` for those.
- Use only the enabled tools in this workflow (`bash`, `edit`, `agentic-workflows`, and safe-outputs). Do not call unsupported `read`/`shell` tools.
- Do not run git branch/stage/commit commands in `bash` (`git checkout -b`, `git add`, `git commit`, `git push`); `create_pull_request` handles branching and commit creation automatically.
- Use only the enabled tools in this workflow (`bash`, `edit`, `agentic-workflows`, and safe-outputs). Do not call unsupported `read`/`shell` tools — there is no `read` tool; use `bash` with `cat` to inspect file contents instead.
- Do not run **any** git commands in `bash` — this includes `git checkout`, `git branch`, `git add`, `git commit`, `git push`, `git status`, and any other `git *` sub-command. `create_pull_request` handles branching and commit creation automatically.
- To count characters in bash, use: `echo -n "your string" | wc -c` (not python3, not shell heredoc).

#### Process

Expand Down Expand Up @@ -171,7 +174,7 @@ Body requirements:
- If image URL exists, embed it with markdown image syntax.
- Close with a short call to action pointing to `https://github.com/${{ github.repository }}`.
- Respect metadata limits before opening the PR: `seoDescription` <= 160 chars and `linkedPostText` <= 80 chars.
- Verify limits with a character count check before creating the PR; if either value is too long, revise and re-check.
- Verify limits using bash: `echo -n "your string" | wc -c`; if either value is too long, revise and re-check.

### 6) Open PR

Expand All @@ -184,7 +187,7 @@ PR body must include:
- Summary of highlighted workflow and why it was chosen.
- Links used as evidence (issues/PRs/log/audit references).
- File path of the created blog post.
- Call `create_pull_request` directly after writing the file; do not run git commands first.
- Call `create_pull_request` directly after writing the file; do not run any git commands first.

### 7) No-action rule

Expand Down