Skip to content

Document create-discussion announcement-capable category requirement #15512

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 2 commits into from
Feb 13, 2026
Merged

Document create-discussion announcement-capable category requirement #15512

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d9c53fb
Initial plan
Copilot Feb 13, 2026
c9d4d13
Add documentation for create-discussion announcement requirement and …
Copilot Feb 13, 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
11 changes: 11 additions & 0 deletions docs/src/content/docs/reference/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -229,6 +229,17 @@ Yes! Use [TrialOps](/gh-aw/patterns/trialops/) to test workflows in isolated tri

See [Common Issues](/gh-aw/troubleshooting/common-issues/) for detailed troubleshooting guidance including workflow failures, debugging strategies, permission issues, and network problems.

### Why is my create-discussion workflow failing with integration-forbidden?

Discussion creation requires announcement-capable categories. If your workflow fails with an `integration-forbidden` error, ensure the `category` field in your configuration specifies a category that has announcement capabilities enabled in your repository's discussion settings.

Common issues:
- **Non-announcement categories**: Only categories configured to support announcements can be used for automated discussion creation. Check your repository's discussion settings to verify which categories have announcement capabilities.
- **Category name typos**: Verify the category name spelling in your workflow configuration matches exactly with your repository's discussion categories. Category names are case-sensitive.
- **Category slugs**: Use lowercase category slugs (e.g., `general`, `announcements`) rather than display names for better reliability.
Copy link

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The example includes "general" as a category slug option, but the FAQ entry and warning state that only announcement-capable categories work. Including "general" as an example may mislead users since it's not typically an announcement-capable category. Consider using only "announcements" as the example, or clarifying that "general" should only be used if it has announcement capabilities enabled in the specific repository.

Suggested change
- **Category slugs**: Use lowercase category slugs (e.g., `general`, `announcements`) rather than display names for better reliability.
- **Category slugs**: Use lowercase category slugs (e.g., `announcements`) rather than display names for better reliability.

Copilot uses AI. Check for mistakes.

If discussions are not enabled or the category lacks announcement capabilities, consider using `fallback-to-issue: true` (the default) to automatically create an issue instead. See [Discussion Creation](/gh-aw/reference/safe-outputs/#discussion-creation-create-discussion) for configuration details.

## Workflow Design

### Should I focus on one workflow, or write many different ones?
Expand Down
3 changes: 3 additions & 0 deletions docs/src/content/docs/reference/safe-outputs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -847,6 +847,9 @@ Creates discussions with optional `category` (slug, name, or ID; defaults to fir

**Category Naming Standard**: Use lowercase, plural category names (e.g., `audits`, `general`, `reports`) for consistency and better searchability. GitHub Discussion category IDs (starting with `DIC_`) are also supported.

> [!WARNING]
> Only announcement-capable category succeeds; all non-announcement categories fail with integration-forbidden.
Copy link

Copilot AI Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The warning message uses singular "category" but should use plural "categories" for grammatical correctness. Suggest changing to: "Only announcement-capable categories succeed; all non-announcement categories fail with integration-forbidden."

Suggested change
> Only announcement-capable category succeeds; all non-announcement categories fail with integration-forbidden.
> Only announcement-capable categories succeed; all non-announcement categories fail with integration-forbidden.

Copilot uses AI. Check for mistakes.

```yaml wrap
safe-outputs:
create-discussion:
Expand Down