Since the 2026-10-13 changelog, a GitHub App can create repositories with repository_creation: write, without administration: write. The changelog says: "When the repository is created, the app or user that created it will be given access to it." In my tests, it isn't.

Setup: an org on the Free plan; a private, org-owned GitHub App with contents: write, metadata: read and repository_creation: write; installed on "Only select repositories" (two repositories).

Steps:

1. With an installation access token, POST /orgs/{org}/repos with {"name": "...", "private": true, "auto_init": true} returns 201, and the repository is created.
2. With a fresh installation token, seconds and then minutes later, GET /installation/repositories doesn't list the new repository.
3. PUT /repos/{org}/{new}/contents/file.txt returns 404.
4. POST /repos/{org}/{template}/generate returns 422 "Could not clone: Cloning user does not have permission to view the clone repository", though the template is among the selected repositories. The new repository is created empty.

Control: the same with an app that has administration: write instead of repository_creation: write, also on selected repositories. The new repository appears in GET /installation/repositories within seconds, and the app writes to it (201).

Expected: with repository_creation: write, the app reaches the repository it created, as it does with administration: write, so it can use it without an org owner adding it by hand.

Question: is this a bug, or is the access given some other way (another endpoint, header or API version)?

Tested on 2026-10-20.