File: content/manuals/enterprise/security/oidc-connections/rulesets-claims.md
Issue
The documentation describes a GitHub feature change that has already occurred as if it's still in the future:
GitHub repositories created after July 15, 2026 have immutable
identifiers in the default subject claim.
Today is July 22, 2026, so July 15, 2026 has already passed. The note uses present tense ("have") which is correct, but the framing with "after July 15, 2026" makes readers uncertain whether this applies to repositories they're creating today.
Why this matters
Readers creating repositories today (July 22, 2026 or later) need to know whether their repositories will have immutable identifiers. The current framing requires them to calculate whether "after July 15, 2026" includes today, when the documentation should clearly state this is the current behavior.
Suggested fix
Reframe to acknowledge this is now the standard behavior:
GitHub repositories created after July 15, 2026 have immutable identifiers in the default subject claim. If you're creating a repository today, it will use this format: repo:octocat@123456/my-repo@456789:ref:refs/heads/main. See the GitHub changelog for more details.
Or more simply:
GitHub now includes immutable identifiers in the default subject claim for repositories created after July 15, 2026. For example: repo:octocat@123456/my-repo@456789:ref:refs/heads/main. See the GitHub changelog for more details.
Found by nightly documentation quality scanner
File:
content/manuals/enterprise/security/oidc-connections/rulesets-claims.mdIssue
The documentation describes a GitHub feature change that has already occurred as if it's still in the future:
Today is July 22, 2026, so July 15, 2026 has already passed. The note uses present tense ("have") which is correct, but the framing with "after July 15, 2026" makes readers uncertain whether this applies to repositories they're creating today.
Why this matters
Readers creating repositories today (July 22, 2026 or later) need to know whether their repositories will have immutable identifiers. The current framing requires them to calculate whether "after July 15, 2026" includes today, when the documentation should clearly state this is the current behavior.
Suggested fix
Reframe to acknowledge this is now the standard behavior:
Or more simply:
Found by nightly documentation quality scanner