Update daily-* and weekly-* agentic workflows to use create-discussion instead of create-issue

[Copilot]

Summary

This PR migrates all daily-* and weekly-* agentic workflows from using GitHub Issues to GitHub Discussions for their planning, status, and research outputs. This change provides better organization and separation between actionable work items (Issues) and collaborative planning/discussion content (Discussions).

Changes Made

Workflows Updated (10 files)

All daily-* and weekly-* workflow files have been updated:

• daily-plan.md
• daily-team-status.md
• daily-test-improver.md
• daily-progress.md
• daily-perf-improver.md
• daily-qa.md
• daily-backlog-burner.md
• daily-accessibility-review.md
• daily-dependency-updates.md
• weekly-research.md

Frontmatter Changes

Updated safe-outputs configuration to use:

• create-discussion instead of create-issue
• Added category parameter with appropriate discussion category slugs

Note: The update-discussion safe-output is not currently supported in gh-aw, so discussions cannot be updated after creation. Workflows have been adjusted to add comments with updated plans instead.

Category assignments:

• announcements - For status updates and planning reports
  • daily-plan, daily-team-status, daily-dependency-updates
• ideas - For research findings, improvement proposals, and development plans
  • weekly-research, daily-test-improver, daily-progress, daily-perf-improver, daily-backlog-burner
• q-a - For quality assurance and accessibility findings
  • daily-qa, daily-accessibility-review

Prompt Updates

Updated workflow prompts to reference "discussions" instead of "issues" where appropriate:

• Changed from "open issue with label X" to "open discussion with title starting with Y"
• Updated search methods from search_issues to search_discussions
• Modified instructions to create discussions instead of issues
• Updated plan refresh logic to add comments with updated plans (since discussions can't be updated)
• Clarified wording for planning discussion updates

Important: Actual bug reports and feature requests still correctly use GitHub Issues. Only planning, status, and research outputs now use Discussions.

Compilation

All workflows have been compiled with gh aw compile and successfully validated. The generated .lock.yml files are gitignored per repository conventions.

New File: TODO.md

Created comprehensive setup instructions including:

• List of required discussion categories (announcements, ideas, q-a)
• Step-by-step guide for creating the categories
• Mapping of which workflows use which categories
• Important notes about category slug requirements

Setup Required

Before these workflows can be used, repository maintainers must:

1. Enable GitHub Discussions (if not already enabled)
2. Create the three required discussion categories with exact slugs:
   • announcements
   • ideas
   • q-a

See TODO.md for detailed instructions.

Benefits

• Better organization: Separates collaborative discussion content from actionable work items
• Improved discoverability: Research and planning content is easier to find in Discussions
• Clearer workflow: Issues remain focused on bugs and feature implementations
• Community friendly: Discussions are more welcoming for open-source collaboration

Original prompt

Update the daily-* and weekly-* agentic workflows to use create-discussion instead of create-issue.

• update frontmatter and pick a relevant category slug
• update prompts
• if possible, create the categories in discussions otherwise, generate a TODO list for the user in TODO.md.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[pelikhan]

@copilot if you change Agentic workflows, you must run the compiler

gh aw compile

see instructions on how to install

[Copilot]

@copilot if you change Agentic workflows, you must run the compiler

gh aw compile...

Done! Compiled all workflows with gh aw compile --workflows-dir workflows. All 15 workflows compiled successfully.

Also discovered that update-discussion is not currently supported, so I removed it from the frontmatter and updated the prompts to add comments with updated plans instead of trying to update discussion bodies.

Commit: 7f60b74

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• githubnext.github.io
  • Triggering command: curl -s REDACTED (dns block)
• https://api.github.com/repos/githubnext/gh-aw/releases/latest
  • Triggering command: curl -s REDACTED (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)