-
-
Notifications
You must be signed in to change notification settings - Fork 10
bug(issue): Post-IssueComment fails with 403 (Resource not accessible by integration) #643
Copy link
Copy link
Closed
Labels
area-infrastructureBuild, CI/CD, configurationBuild, CI/CD, configurationarea-skillsSkills documentation and patternsSkills documentation and patternsarea-workflowsGitHub Actions workflowsGitHub Actions workflowsbugSomething isn't workingSomething isn't workinggithub-actionsGitHub Actions workflow updatesGitHub Actions workflow updatespriority:P0Critical: Blocks core functionality, security vulnerability, or data lossCritical: Blocks core functionality, security vulnerability, or data loss
Metadata
Metadata
Assignees
Labels
area-infrastructureBuild, CI/CD, configurationBuild, CI/CD, configurationarea-skillsSkills documentation and patternsSkills documentation and patternsarea-workflowsGitHub Actions workflowsGitHub Actions workflowsbugSomething isn't workingSomething isn't workinggithub-actionsGitHub Actions workflow updatesGitHub Actions workflow updatespriority:P0Critical: Blocks core functionality, security vulnerability, or data lossCritical: Blocks core functionality, security vulnerability, or data loss
Problem\nPost-IssueComment.ps1 can fail with HTTP 403 Resource not accessible by integration when posting an issue comment. This blocks tooling that relies on comments for follow-ups or corrections.\n\n## Observed behavior\n- Posting to repos/OWNER/REPO/issues/ISSUE/comments returns 403.\n- Issue creation may still succeed in the same environment.\n\n## Request\nImprove diagnostics and fallback behavior:\n- Detect 403 and output a clear explanation of likely causes (token type, GitHub App vs user token permissions).\n- Provide an alternative action when comments are not permitted (example: write the intended payload to a local artifact for manual posting, or fail with a structured error).\n\n## Acceptance criteria\n- 403 failures are reported with actionable guidance and a structured error payload.