Skip to content

Commit 4b06fa0

Browse files
talumCopilot
andcommitted
Update pull request artifacts feature flag documentation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 633fd653-7701-48a8-8eec-934b966469a3
1 parent 4517fd9 commit 4b06fa0

1 file changed

Lines changed: 0 additions & 8 deletions

File tree

‎docs/feature-flags.md‎

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -156,14 +156,6 @@ Enable `--features=pull_request_artifacts` (or
156156
mode. Read-only mode exposes only the read tool. Both tools reject calls in
157157
lockdown mode.
158158

159-
The MCP exposure flag `pull_request_artifacts` is separate from GitHub's
160-
`pull_request_artifacts_api` rollout flag. **The API checks the rollout flag
161-
for the target repository, with organization context, on every operation.**
162-
Enabling the MCP flag does not enable the API for a repository. The tools do
163-
not substitute a per-user feature check or cache repository rollout decisions.
164-
A 404 can mean a disabled rollout, missing resource, or insufficient access;
165-
it is not interpreted as a definitive flag status.
166-
167159
All operations require `owner`, `repo`, and `pull_number`. The tools resolve
168160
the repository's numeric ID and use the configured authenticated GitHub
169161
client and API base URL. They declare `repo` in OAuth challenge metadata;

0 commit comments

Comments
 (0)