Skip to content

Add Discord security audit 2026 role - #248

Open
claude[bot] wants to merge 1 commit into
mainfrom
claude/security-audit-2026-role
Open

claude[bot] wants to merge 1 commit into
mainfrom
claude/security-audit-2026-role

Conversation

@claude

@claude claude Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Requested by Paul Carleton · Slack thread

Before: There is no Discord role for the external auditors from OSTIF and X41 D-Sec who are working on the 2026 security audit, so there is nothing to grant them (or to gate a channel on) short of giving them a maintainer role.

After: A new Discord-only role, security audit 2026 (synced), exists for those auditors. It carries no permissions of its own and nobody is in it yet; people are added by putting ROLE_IDS.SECURITY_AUDIT_2026 in their memberOf in src/config/users.ts.

How: Adds SECURITY_AUDIT_2026: 'security-audit-2026' to src/config/roleIds.ts and the matching role entry to src/config/roles.ts, next to release-managers and following that precedent (#242). The role is Discord-only: no GitHub team, no Google group, no repo access, no provisionUser, no Discord permissions, and it does not imply (and is not implied by) any other role. On merge, the deploy creates the Discord role security audit 2026 (synced) with an empty permission set; nothing else changes. No members are added in this PR, and no Discord channel is added or changed: this repository does not manage channel permission overwrites, so letting the role see a channel is a separate step in Discord.

This PR was drafted with AI assistance (Claude Code).

Add a Discord-only security-audit-2026 role (Discord role
"security audit 2026 (synced)") for the external auditors from OSTIF and
X41 D-Sec working on the 2026 security audit. It has no GitHub team,
Google group or repo access and implies no other role, following the
release-managers precedent. No members are added yet.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016HDqNaSyEqCamYANSddJar
@claude
claude Bot requested a review from a team as a code owner November 16, 2026 16:47
@claude

claude Bot commented Nov 16, 2026

Copy link
Copy Markdown
Contributor Author

The red Preview Changes check is not caused by this diff. The job failed before running any step because the production environment rejected the PR ref; its two annotations read:

Branch "refs/pull/248/merge" is not allowed to deploy to production due to environment protection rules.

The deployment was rejected or didn't satisfy other protection rules.

Build and Typecheck and CodeQL pass, and npm run check passes locally (87 tests). A repo admin needs to allow PR refs in the environment's deployment rules or re-run the job.


Generated by Claude Code

This branch had an error being deployed

1 failed deployment
production — 87b1aa10 Deployed Nov 16, 2026 by claude[bot] via Preview Changes #414
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant