Fix GitHub pro upgrade flow#44903
Open
ashis-baral wants to merge 6 commits into
Open
Conversation
Updated codeNavigation status for C and C++ languages to 'supported'.
|
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. |
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 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. |
This comment was marked as spam.
This comment was marked as spam.
Contributor
|
@ashis-baral Can I get more details on what you were trying to do? Because "Additional billing details" absolutely does still exist, and this reusable is used in a lot of places. It's unlikely this change would be correct for all of them, so I need to know what you were trying to do so we can consider a more targeted change. |
Author
|
@Sharra-writes Thanks for asking! I tested the GitHub Pro upgrade flow using the steps in the documentation: https://docs.github.com/en/billing/how-tos/manage-plan-and-licenses/upgrade-plan. On my personal account, when I navigated to Settings → Billing and licensing, I found the Upgrade to GitHub Pro option on the Licensing page. That's why I changed the instructions to point to Licensing. I also noticed that Additional billing details still exists in the sidebar, so my intention wasn't to say that it had been removed. My goal was only to make the navigation match the GitHub Pro upgrade flow that I tested. 
I've attached screenshots showing both the Licensing page (where the upgrade option appears) and the Additional billing details page for context. |
|
Yritan saada laskeman tuotanto laskemia bitcomin muu arvion
timohepp
la 11.7.2026 klo 6.19 Ashis Kumar Baral ***@***.***>
kirjoitti:
… *ashis-baral* left a comment (github/docs#44903)
<#44903 (comment)>
@Sharra-writes <https://github.com/Sharra-writes> Thanks for asking! I
tested the GitHub Pro upgrade flow using the steps in the documentation:
https://docs.github.com/en/billing/how-tos/manage-plan-and-licenses/upgrade-plan
.
On my personal account, when I navigated to Settings → Billing and
licensing, I found the Upgrade to GitHub Pro option on the Licensing page.
That's why I changed the instructions to point to Licensing.
I also noticed that Additional billing details still exists in the
sidebar, so my intention wasn't to say that it had been removed. My goal
was only to make the navigation match the GitHub Pro upgrade flow that I
tested.
additional.billing.details.png (view on web)
<https://github.com/user-attachments/assets/004c1e33-ec77-419c-b78f-68d38c82460c>
licensingg.png (view on web)
<https://github.com/user-attachments/assets/49147049-20af-4cbe-b6a6-1a09c87d9d29>
I've attached screenshots showing both the Licensing page (where the
upgrade option appears) and the Additional billing details page for context.
—
Reply to this email directly, view it on GitHub
<#44903?email_source=notifications&email_token=CHZY3J2RNYDDP35A7US7VBD5EGW2PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJUGIYDCMJYG4Z2M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4942011873>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CHZY3JZ37K2CYCMQC6QVCJD5EGW2PAVCNFSNUABFKJSXA33TNF2G64TZHMYTQOJWGIYTMMBXHNEXG43VMU5TINZTGY3DSMJXGA4KC5QC>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/CHZY3J6MDWBTNF36PZXVTL35EGW2PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJUGIYDCMJYG4Z2M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSVGM33PORSXEX3JN5ZQ>
and Android
<https://github.com/notifications/mobile/android/CHZY3J6GQ5MXU7KHUWVZGFD5EGW2PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJUGIYDCMJYG4Z2M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>.
Download it today!
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
Rakenta oma puhelimen radio vastan ottimen ohjelmalla
timohepp
la 11.7.2026 klo 9.01 Timo Hepp ***@***.***> kirjoitti:
… Yritan saada laskeman tuotanto laskemia bitcomin muu arvion
timohepp
la 11.7.2026 klo 6.19 Ashis Kumar Baral ***@***.***>
kirjoitti:
> *ashis-baral* left a comment (github/docs#44903)
> <#44903 (comment)>
>
> @Sharra-writes <https://github.com/Sharra-writes> Thanks for asking! I
> tested the GitHub Pro upgrade flow using the steps in the documentation:
> https://docs.github.com/en/billing/how-tos/manage-plan-and-licenses/upgrade-plan
> .
>
> On my personal account, when I navigated to Settings → Billing and
> licensing, I found the Upgrade to GitHub Pro option on the Licensing page.
> That's why I changed the instructions to point to Licensing.
>
> I also noticed that Additional billing details still exists in the
> sidebar, so my intention wasn't to say that it had been removed. My goal
> was only to make the navigation match the GitHub Pro upgrade flow that I
> tested.
> additional.billing.details.png (view on web)
> <https://github.com/user-attachments/assets/004c1e33-ec77-419c-b78f-68d38c82460c>
> licensingg.png (view on web)
> <https://github.com/user-attachments/assets/49147049-20af-4cbe-b6a6-1a09c87d9d29>
>
> I've attached screenshots showing both the Licensing page (where the
> upgrade option appears) and the Additional billing details page for context.
>
> —
> Reply to this email directly, view it on GitHub
> <#44903?email_source=notifications&email_token=CHZY3J2RNYDDP35A7US7VBD5EGW2PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJUGIYDCMJYG4Z2M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4942011873>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/CHZY3JZ37K2CYCMQC6QVCJD5EGW2PAVCNFSNUABFKJSXA33TNF2G64TZHMYTQOJWGIYTMMBXHNEXG43VMU5TINZTGY3DSMJXGA4KC5QC>
> .
> Triage notifications, keep track of coding agent tasks and review pull
> requests on the go with GitHub Mobile for iOS
> <https://github.com/notifications/mobile/ios/CHZY3J6MDWBTNF36PZXVTL35EGW2PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJUGIYDCMJYG4Z2M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSVGM33PORSXEX3JN5ZQ>
> and Android
> <https://github.com/notifications/mobile/android/CHZY3J6GQ5MXU7KHUWVZGFD5EGW2PA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJUGIYDCMJYG4Z2M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>.
> Download it today!
> You are receiving this because you are subscribed to this thread.Message
> ID: ***@***.***>
>
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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: