Skip to content

Fix GitHub pro upgrade flow#44903

Open
ashis-baral wants to merge 5 commits into
github:mainfrom
ashis-baral:fix-github-pro-upgrade-flow
Open

Fix GitHub pro upgrade flow#44903
ashis-baral wants to merge 5 commits into
github:mainfrom
ashis-baral:fix-github-pro-upgrade-flow

Conversation

@ashis-baral

Copy link
Copy Markdown

Why:

The current documentation contains outdated billing and upgrade instructions that do not match the current GitHub UI.

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

Updated the billing navigation from "Additional billing details" to "Licensing".

Check off the following:

  • 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.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

@welcome

welcome Bot commented Jun 24, 2026

Copy link
Copy Markdown

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 github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Jun 24, 2026
@github-actions

github-actions Bot commented Jun 24, 2026

Copy link
Copy Markdown
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
billing/how-tos/manage-plan-and-licenses/downgrade-plan.md fpt
ghec
fpt
ghec
from reusable
billing/how-tos/manage-plan-and-licenses/manage-pending-changes.md fpt
ghec
fpt
ghec
from reusable
billing/how-tos/manage-plan-and-licenses/upgrade-plan.md fpt
ghec
fpt
ghec
from reusable
billing/how-tos/pay-third-parties/cancel-marketplace-app.md fpt
ghec
fpt
ghec
from reusable
billing/how-tos/pay-third-parties/cancel-sponsorship.md fpt
ghec
fpt
ghec
from reusable
billing/how-tos/pay-third-parties/downgrade-marketplace-app.md fpt
ghec
fpt
ghec
from reusable
billing/how-tos/pay-third-parties/upgrade-marketplace-app.md fpt
ghec
fpt
ghec
from reusable

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

🤖 This comment is automatically generated.

@ashis-baral ashis-baral deleted the fix-github-pro-upgrade-flow branch June 24, 2026 19:13
@ashis-baral ashis-baral restored the fix-github-pro-upgrade-flow branch June 24, 2026 19:19
@ashis-baral ashis-baral reopened this Jun 24, 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