Skip to content

[Fundamentals] Add GitHub Secret Scanning details to token formats page#29715

Open
ethulia wants to merge 1 commit intoproductionfrom
mlu/scannable-tokens-secret-scanning
Open

[Fundamentals] Add GitHub Secret Scanning details to token formats page#29715
ethulia wants to merge 1 commit intoproductionfrom
mlu/scannable-tokens-secret-scanning

Conversation

@ethulia
Copy link
Copy Markdown
Contributor

@ethulia ethulia commented Apr 9, 2026

Summary

Screenshots (optional)

Documentation checklist

  • Is there a changelog entry (guidelines)? If you don't add one for something awesome and new (however small) — how will our customers find out? Changelogs are automatically posted to RSS feeds, the Discord, and X.
  • The change adheres to the documentation style guide.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 9, 2026

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/docs/fundamentals/ @dcpena, @cloudflare/pcx-technical-writing

@ethulia
Copy link
Copy Markdown
Contributor Author

ethulia commented Apr 9, 2026

/bonk review this

@ethulia ethulia requested a review from haleycode April 9, 2026 04:20
Copy link
Copy Markdown
Contributor

@ask-bonk ask-bonk bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found. The changes add clear, accurate details about GitHub Secret Scanning behavior and follow the documentation style guide.

@ask-bonk
Copy link
Copy Markdown
Contributor

ask-bonk bot commented Apr 9, 2026

No issues found. The changes add clear, accurate details about GitHub Secret Scanning behavior and follow the documentation style guide.

Review summary:

  • MDX syntax is valid with no unescaped characters
  • Frontmatter fields are correct
  • External link to GitHub docs is appropriate
  • Heading hierarchy is properly structured (H2 → H3)
  • Active voice used throughout, no contractions
  • Content accurately distinguishes between public and private repository handling

Approved — PR is ready for merge.

github run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants