Conversation
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
subatoi
left a comment
There was a problem hiding this comment.
Thanks for your interest in the GItHub docs—I'll get this merged now
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
Why:
Closes:
N/A
Standardizing product name variables to ensure documentation consistency and maintainability. In
content/integrations/concepts/github-developer-program.md, hardcoded "GitHub" strings remained in a section heading and in link text while the rest of the document uses{% data variables.product.github %}(aligned with PR #42511). This change normalizes the remaining occurrences to align with the GitHub Docs style guide's single-source-of-truth principle.What's being changed:
In
content/integrations/concepts/github-developer-program.md:## Have an integration that works with GitHub?with## Have an integration that works with {% data variables.product.github %}?.[Octocat or GitHub logo]with[Octocat or {% data variables.product.github %} logo].Check off the following: