Code of Conduct
What article on docs.github.com is affected?
you
What changes are you suggesting?
1000សួស្តី Hj, ឥឡូវនេះ SAING CHANNAN អញ្ជើញអ្នកឱ្យចូលរួមអាជីវកម្មក្នុងនាមជាអ្នកគិតលុយ។ ចុចលីងខាងក្រោម ដើម្បីដំណើរការ ABA Merchant app របស់អ្នកក្នុងរយៈពេល 72 ម៉ោង:
https://pwapp.ababank.com/pw-app/deeplink/register?register_key=FhEeFukPQfukw8t8dMmv%2Bw%3D%3D
Additional information
500# Troubleshooting the 2---
title: Upgrading your account's plan
intro: 'You can upgrade the plan for a personal account or organization on {% data variables.product.prodname_dotcom %} at any time.'
redirect_from:
- /github/setting-up-and-managing-billing-and-payments-on-github/upgrading-your-github-subscription
- /articles/upgrading-your-personal-account-s-billing-plan
- /articles/upgrading-your-personal-account
- /articles/upgrading-your-personal-account-from-free-to-a-paid-account
- /articles/upgrading-your-personal-account-from-free-to-paid-with-a-credit-card
- /articles/upgrading-your-personal-account-from-free-to-paid-with-paypal
- /articles/500-error-while-upgrading
- /articles/upgrading-your-organization-s-billing-plan
- /articles/changing-your-organization-billing-plan
- /articles/upgrading-your-organization-account-from-free-to-paid-with-a-credit-card
- /articles/upgrading-your-organization-account-from-free-to-paid-with-paypal
- /articles/upgrading-your-organization-account
- /articles/switching-from-per-repository-to-per-user-pricing
- /articles/adding-seats-to-your-organization
- /articles/upgrading-your-github-billing-plan
- /articles/upgrading-your-github-subscription
- /github/setting-up-and-managing-billing-and-payments-on-github/managing-billing-for-your-github-account/upgrading-your-github-subscription
- /billing/managing-billing-for-your-github-account/upgrading-your-github-subscription
- /billing/managing-the-plan-for-your-github-account/upgrading-your-accounts-plan
versions:
fpt: ''
ghec: ''
shortTitle: Upgrade plan
contentType: how-tos
category:
- Manage your plan and licenses
Upgrading your personal account's plan
You can upgrade your personal account from {% data variables.product.prodname_free_user %} to {% data variables.product.prodname_pro %} to get advanced code review tools on private repositories owned by your personal account.
Upgrading your personal account does not affect any organizations you may manage or repositories owned by those organizations. {% data reusables.gated-features.more-info %}
{% data reusables.user-settings.access_settings %}
{% data reusables.user-settings.billing_plans %}
- Next to "Current plan", click Upgrade.
- Under "Pro" on the "Compare plans" page, click Upgrade to Pro.
{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
{% data reusables.dotcom_billing.show-plan-details %}
{% data reusables.dotcom_billing.enter-billing-info %}
{% data reusables.dotcom_billing.enter-payment-info %}
{% data reusables.dotcom_billing.finish_upgrade %}
Upgrading your organization's plan
You can upgrade your organization from {% data variables.product.prodname_free_team %} for an organization to {% data variables.product.prodname_team %} to access advanced collaboration and management tools for teams, or upgrade your organization to {% data variables.product.prodname_ghe_cloud %} for additional security, compliance, and deployment controls.
Upgrading an organization does not affect your personal account or repositories owned by your personal account. {% data reusables.gated-features.more-info-org-products %}
{% data reusables.dotcom_billing.org-billing-perms %}
{% data reusables.organizations.billing-settings %}
{% data reusables.dotcom_billing.upgrade_org %}
{% data reusables.dotcom_billing.choose_org_plan %}
{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
{% data reusables.dotcom_billing.show-plan-details %}
{% data reusables.dotcom_billing.enter-payment-info %}
{% data reusables.dotcom_billing.owned_by_business %}
{% data reusables.dotcom_billing.finish_upgrade %}
Next steps for organizations using {% data variables.product.prodname_ghe_cloud %}
As part of your upgrade to {% data variables.product.prodname_ghe_cloud %}, you set up an enterprise account. An enterprise account allows you to manage multiple organizations. Optionally, you can set up identity and access management for an individual organization or enterprise account. See AUTOTITLE and AUTOTITLE{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %}
{% data reusables.enterprise.create-an-enterprise-account %} See AUTOTITLE{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %}
[!NOTE] {% data reusables.actions.org-to-enterprise-actions-permissions %}
Troubleshooting a 500 error when upgrading
{% data reusables.dotcom_billing.500-error %}
Switching your organization from per-repository to per-user pricing
{% data reusables.dotcom_billing.switch-legacy-billing %} See AUTOTITLE.
{% data reusables.organizations.billing-settings %}
- To the right of your plan name, select the Edit dropdown menu, then click Edit plan.
- To the right of "Advanced tools for teams", click Upgrade now.
{% data reusables.dotcom_billing.choose_org_plan %}
{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
{% data reusables.dotcom_billing.owned_by_business %}
{% data reusables.dotcom_billing.finish_upgrade %}
Further reading
Learn how to work around the 2 GiB push limit.
About the push limit
GitHub has a maximum 2 GiB limit for a single push. You might hit this limit when trying to upload very large repositories for the first time, importing large repositories from other platforms, or when trying to rewrite the history of large existing repositories.
If you hit this limit, you may see one of the following error messages:
fatal: the remote end hung up unexpectedlyremote: fatal: pack exceeds maximum allowed size
You can either split up your push into smaller parts, or delete the Git history and start from scratch. If you have made a single commit that's larger than 2 GiB and you can't delete the Git history and start from scratch, then you will need to perform an interactive rebase to split the large commit into multiple smaller ones.
Splitting up a large push
You can avoid hitting the limit by breaking your push into smaller parts, each of which should be under 2 GiB in size. If a branch is within this size limit, you can push it all at once. However, if a branch is larger than 2 GiB, you'll need to split the push into even smaller portions and push only a few commits at a time.
-
If you haven't configured the remote yet, add the repository as a new remote. For more information, see Managing remote repositories.
-
To find suitable commits spread out along the history of the main branch in your local repository, run the following command:
git log --oneline --reverse refs/heads/BRANCH-NAME | awk 'NR % 1000 == 0'
This command reveals every 1000th commit. You can increase or decrease the number to adjust the step size.
-
Push each of these commits one at a time to your GitHub hosted repository.
git push REMOTE-NAME +<YOUR_COMMIT_SHA_NUMBER>:refs/heads/BRANCH-NAME
If you see the message remote: fatal: pack exceeds maximum allowed size, reduce the step size in step 2 and try again.
-
Go through the same process for every commit you identified in the history from step 2.
-
If this is the first time this repository is being pushed to GitHub, perform a final mirror push to ensure any remaining refs are pushed up.
git push REMOTE-NAME --mirror
If this is still too large, you'll need to push up other branches in stages using the same steps.
Once you're familiar with the procedure, you can automate steps 2 to 4 to simplify the process. For example:
step_commits=$(git log --oneline --reverse refs/heads/BRANCH-NAME | awk 'NR % 1000 == 0')
echo "$step_commits" | while read commit message; do git push REMOTE-NAME +$commit:refs/heads/BRANCH-NAME; done
Starting from scratch
If the repository does not have any history, or your initial commit was over 2 GiB on its own and you don't mind resetting the Git history, you can also start from scratch.
-
On your local copy, delete the hidden .git folder to remove all the previous Git history and convert it back into a normal folder full of files.
-
Create a new empty folder.
-
Run git init and git lfs install on the new folder, and add the new empty GitHub repository as a remote.
-
If you already use Git Large File Storage and have all of the Git LFS tracking rules you intend to use already listed in the .gitattributes file in the old folder, that should be the first file you copy across to the new folder. You should ensure the tracking rules are in place before you add any other files, so that there's no chance things intended for Git LFS will be committed to regular Git storage.
If you do not already use Git LFS, you can skip this step, or you can set up the tracking rules you intend to use in the .gitattributes file in the new folder before you copy any other files across. For more information, see Configuring Git Large File Storage.
-
Move batches of files that are smaller than 2 GiB from the old folder to the new folder. After each batch is moved, create a commit and push it before moving the next batch. You can take a cautious approach and stick to around 2 GiB. Alternatively, if you have a folder with files meant for Git LFS, you can ignore those files when considering the 2 GiB limit per batch.
Once the old folder is empty, the GitHub repository should contain everything. If you are using Git LFS, all files meant for Git LFS should be pushed to Git LFS storage.](url)
Code of Conduct
What article on docs.github.com is affected?
you
What changes are you suggesting?
1000សួស្តី Hj, ឥឡូវនេះ SAING CHANNAN អញ្ជើញអ្នកឱ្យចូលរួមអាជីវកម្មក្នុងនាមជាអ្នកគិតលុយ។ ចុចលីងខាងក្រោម ដើម្បីដំណើរការ ABA Merchant app របស់អ្នកក្នុងរយៈពេល 72 ម៉ោង:
https://pwapp.ababank.com/pw-app/deeplink/register?register_key=FhEeFukPQfukw8t8dMmv%2Bw%3D%3D
Additional information
500# Troubleshooting the 2---
title: Upgrading your account's plan
intro: 'You can upgrade the plan for a personal account or organization on {% data variables.product.prodname_dotcom %} at any time.'
redirect_from:
versions:
fpt: ''
ghec: ''
shortTitle: Upgrade plan
contentType: how-tos
category:
Upgrading your personal account's plan
You can upgrade your personal account from {% data variables.product.prodname_free_user %} to {% data variables.product.prodname_pro %} to get advanced code review tools on private repositories owned by your personal account.
Upgrading your personal account does not affect any organizations you may manage or repositories owned by those organizations. {% data reusables.gated-features.more-info %}
{% data reusables.user-settings.access_settings %}
{% data reusables.user-settings.billing_plans %}
{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
{% data reusables.dotcom_billing.show-plan-details %}
{% data reusables.dotcom_billing.enter-billing-info %}
{% data reusables.dotcom_billing.enter-payment-info %}
{% data reusables.dotcom_billing.finish_upgrade %}
Upgrading your organization's plan
You can upgrade your organization from {% data variables.product.prodname_free_team %} for an organization to {% data variables.product.prodname_team %} to access advanced collaboration and management tools for teams, or upgrade your organization to {% data variables.product.prodname_ghe_cloud %} for additional security, compliance, and deployment controls.
Upgrading an organization does not affect your personal account or repositories owned by your personal account. {% data reusables.gated-features.more-info-org-products %}
{% data reusables.dotcom_billing.org-billing-perms %}
{% data reusables.organizations.billing-settings %}
{% data reusables.dotcom_billing.upgrade_org %}
{% data reusables.dotcom_billing.choose_org_plan %}
{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
{% data reusables.dotcom_billing.show-plan-details %}
{% data reusables.dotcom_billing.enter-payment-info %}
{% data reusables.dotcom_billing.owned_by_business %}
{% data reusables.dotcom_billing.finish_upgrade %}
Next steps for organizations using {% data variables.product.prodname_ghe_cloud %}
As part of your upgrade to {% data variables.product.prodname_ghe_cloud %}, you set up an enterprise account. An enterprise account allows you to manage multiple organizations. Optionally, you can set up identity and access management for an individual organization or enterprise account. See AUTOTITLE and AUTOTITLE{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %}
{% data reusables.enterprise.create-an-enterprise-account %} See AUTOTITLE{% ifversion fpt %} in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}.{% endif %}
Troubleshooting a 500 error when upgrading
{% data reusables.dotcom_billing.500-error %}
Switching your organization from per-repository to per-user pricing
{% data reusables.dotcom_billing.switch-legacy-billing %} See AUTOTITLE.
{% data reusables.organizations.billing-settings %}
{% data reusables.dotcom_billing.choose_org_plan %}
{% data reusables.dotcom_billing.choose-monthly-or-yearly-billing %}
{% data reusables.dotcom_billing.owned_by_business %}
{% data reusables.dotcom_billing.finish_upgrade %}
Further reading
Learn how to work around the 2 GiB push limit.
About the push limit
GitHub has a maximum 2 GiB limit for a single push. You might hit this limit when trying to upload very large repositories for the first time, importing large repositories from other platforms, or when trying to rewrite the history of large existing repositories.
If you hit this limit, you may see one of the following error messages:
fatal: the remote end hung up unexpectedlyremote: fatal: pack exceeds maximum allowed sizeYou can either split up your push into smaller parts, or delete the Git history and start from scratch. If you have made a single commit that's larger than 2 GiB and you can't delete the Git history and start from scratch, then you will need to perform an interactive rebase to split the large commit into multiple smaller ones.
Splitting up a large push
You can avoid hitting the limit by breaking your push into smaller parts, each of which should be under 2 GiB in size. If a branch is within this size limit, you can push it all at once. However, if a branch is larger than 2 GiB, you'll need to split the push into even smaller portions and push only a few commits at a time.
If you haven't configured the remote yet, add the repository as a new remote. For more information, see Managing remote repositories.
To find suitable commits spread out along the history of the main branch in your local repository, run the following command:
This command reveals every 1000th commit. You can increase or decrease the number to adjust the step size.
Push each of these commits one at a time to your GitHub hosted repository.
If you see the message
remote: fatal: pack exceeds maximum allowed size, reduce the step size in step 2 and try again.Go through the same process for every commit you identified in the history from step 2.
If this is the first time this repository is being pushed to GitHub, perform a final mirror push to ensure any remaining refs are pushed up.
If this is still too large, you'll need to push up other branches in stages using the same steps.
Once you're familiar with the procedure, you can automate steps 2 to 4 to simplify the process. For example:
Starting from scratch
If the repository does not have any history, or your initial commit was over 2 GiB on its own and you don't mind resetting the Git history, you can also start from scratch.
On your local copy, delete the hidden
.gitfolder to remove all the previous Git history and convert it back into a normal folder full of files.Create a new empty folder.
Run
git initandgit lfs installon the new folder, and add the new empty GitHub repository as a remote.If you already use Git Large File Storage and have all of the Git LFS tracking rules you intend to use already listed in the
.gitattributesfile in the old folder, that should be the first file you copy across to the new folder. You should ensure the tracking rules are in place before you add any other files, so that there's no chance things intended for Git LFS will be committed to regular Git storage.If you do not already use Git LFS, you can skip this step, or you can set up the tracking rules you intend to use in the
.gitattributesfile in the new folder before you copy any other files across. For more information, see Configuring Git Large File Storage.Move batches of files that are smaller than 2 GiB from the old folder to the new folder. After each batch is moved, create a commit and push it before moving the next batch. You can take a cautious approach and stick to around 2 GiB. Alternatively, if you have a folder with files meant for Git LFS, you can ignore those files when considering the 2 GiB limit per batch.
Once the old folder is empty, the GitHub repository should contain everything. If you are using Git LFS, all files meant for Git LFS should be pushed to Git LFS storage.](url)