Skip to content

docs: clarify GitHub immutable identifier behavior#25624

Open
devendrakushwah80 wants to merge 2 commits into
docker:mainfrom
devendrakushwah80:docs/clarify-oidc-immutable-identifiers
Open

docs: clarify GitHub immutable identifier behavior#25624
devendrakushwah80 wants to merge 2 commits into
docker:mainfrom
devendrakushwah80:docs/clarify-oidc-immutable-identifiers

Conversation

@devendrakushwah80

@devendrakushwah80 devendrakushwah80 commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Description

Clarifies that GitHub's immutable identifiers in the default subject claim are now described as the current behavior for repositories created after July 15, 2026.

Related issues or tickets

Fixes #25621

Reviews

  • Technical review
  • Editorial review
  • Product review

@netlify

netlify Bot commented Jul 22, 2026

Copy link
Copy Markdown

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 472ea6a
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/6a610e51579b7400088ded2e
😎 Deploy Preview https://deploy-preview-25624--docsdocker.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@akristen akristen self-assigned this Jul 22, 2026
Comment thread content/manuals/enterprise/security/oidc-connections/rulesets-claims.md Outdated
@akristen

Copy link
Copy Markdown
Contributor

Can you unpack what was missing from the original text? Your suggestion sounds pretty similar to the original, but want to honor what might be missing and come up with a good solution!

@devendrakushwah80

Copy link
Copy Markdown
Contributor Author

Thanks for the feedback!

The wording was based on issue #25621. My understanding was that the scanner was flagging the note because it could still read like a future-facing statement, even though July 15, 2026 has already passed.

My intent was simply to make it read more clearly as the current behavior without changing its meaning.

I like your suggested wording—it expresses the current behavior more directly. I'll update the PR accordingly.

…claims.md

Co-authored-by: Alexa Kristensen <81787716+akristen@users.noreply.github.com>
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.

[docs-scanner] Past date framed as future event in OIDC connections docs

2 participants