Skip to content

Conversation

@wd006
Copy link

@wd006 wd006 commented Jan 22, 2026

Why:

Closes:
N/A
Standardizing product name variables to ensure documentation consistency and maintainability. I noticed that several documents were using hardcoded "GitHub" strings or the deprecated prodname_dotcom variable instead of the current standard {% data variables.product.github %}. This refactor aligns with the GitHub Docs style guide's "single-source-of-truth" principle and ensures branding updates can be managed globally.

What's being changed (if available, include any code snippets, screenshots, or gifs):

This PR performs a normalization cleanup of product name variables in the content/integrations directories.

Key Changes:

  • Replaced hardcoded "GitHub" text with {% data variables.product.github %} in body content.
  • Migrated deprecated {% data variables.product.prodname_dotcom %} variables to the preferred github variable.

Check off the following:

  • The changes in this PR meet the docs fundamentals that are required for all content.
  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • All CI checks are passing and the changes look good in the review environment.

wd006 added 2 commits January 22, 2026 22:35
Refactored product name references within the integrations/concepts directory.
Replaced hardcoded strings and deprecated 'prodname_dotcom' variables
with the current standard '{% data variables.product.github %}' to align
with the GitHub Docs style guide and naming conventions.
Refactored product name references within the integrations/index.md directory.
Replaced hardcoded strings and deprecated 'prodname_dotcom' variables
with the current standard '{% data variables.product.github %}' to align
with the GitHub Docs style guide and naming conventions.
@welcome
Copy link

welcome bot commented Jan 22, 2026

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions
Copy link
Contributor

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 links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
integrations/concepts/about-integrations.md fpt
ghec
ghes@ 3.19 3.18 3.17 3.16 3.15 3.14
fpt
ghec
ghes@ 3.19 3.18 3.17 3.16 3.15 3.14
integrations/concepts/featured-github-integrations.md fpt
ghec
ghes@ 3.19 3.18 3.17 3.16 3.15 3.14
fpt
ghec
ghes@ 3.19 3.18 3.17 3.16 3.15 3.14
integrations/concepts/github-developer-program.md fpt
ghec
fpt
ghec
integrations/index.md fpt
ghec
ghes@ 3.19 3.18 3.17 3.16 3.15 3.14
fpt
ghec
ghes@ 3.19 3.18 3.17 3.16 3.15 3.14

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jan 22, 2026
@wd006 wd006 closed this Jan 22, 2026
@wd006 wd006 reopened this Jan 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant