Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repo sync #36022

Merged
merged 4 commits into from
Jan 22, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/workflows/reviewers-docs-engineering.yml
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,7 @@ on:
- '!src/**.json' # So that Docs Engineering isn't reviewing automated pipeline data PRs
- '!src/**.yml' # So that Docs Engineering isn't reviewing automated pipeline data PRs
- '.github/**'
- 'config/**'
- '**Dockerfile'
- 'package*.json'
- .github/workflows/reviewers-docs-engineering.yml
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -51,3 +51,19 @@ You can:
* Download CSV usage reports.

{% endif %}

## Inviting a billing manager

The invited person will receive an invitation email asking them to become a billing manager for your {% ifversion ghec %}enterprise{% endif %}{% ifversion fpt %} organization{% endif %}. Once the invited person clicks the accept link in their invitation email, they will automatically be added to the {% ifversion ghec %}enterprise{% endif %}{% ifversion fpt %} organization{% endif %} as a billing manager. If they don't already have a {% data variables.product.prodname_dotcom %} account, they will be directed to sign up for one, and they will be automatically added to the {% ifversion ghec %}enterprise{% endif %}{% ifversion fpt %} organization{% endif %} as a billing manager after they create an account.

{% data reusables.user-settings.access_settings %}
1. In the "Access" section of the sidebar, click **{% octicon "organization" aria-hidden="true" %} Organizations**.
{% data reusables.profile.org_settings %}
1. If you are an organization owner, in the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
1. Click the link in the text box, **Enterprise account billing settings**, which will direct you to your organizations billing settings page.
1. On the left side of the page, in the enterprise account sidebar, click **{% octicon "person" aria-hidden="true" %} People**.
1. Under "People", click **Administrators**.
1. Above the list of administrators, click **Invite admin**.
1. Type the username, full name, or email address of the person you want to invite, then select the appropriate person from the results.
1. Select **Billing Manager**.
1. Click **Send Invitation**.
Original file line number Diff line number Diff line change
Expand Up @@ -46,14 +46,21 @@ Billing managers **are not** able to:

## Inviting a billing manager

{% ifversion enhanced-billing-platform %}

>[!NOTE] Enterprise accounts, and organizations owned by enterprise accounts, created after June 2, 2024, have access to the enhanced billing platform. Enterprises that participated in the {% data variables.release-phases.public_preview %} program also have access to the enhanced billing platform.
>
> If you are on the enhanced billing platform, the process for adding a billing manager is different. See [AUTOTITLE](/billing/using-the-new-billing-platform/roles-for-the-new-billing-platform#inviting-a-billing-manager).

{% endif %}

{% ifversion ghec %}

> [!NOTE]
> If your organization is owned by an enterprise account, you cannot invite billing managers at the organization level. For more information, see [AUTOTITLE](/admin/overview/about-enterprise-accounts).
If your organization is owned by an enterprise account, you cannot invite billing managers at the organization level. For more information, see [AUTOTITLE](/admin/overview/about-enterprise-accounts).

{% endif %}

The invited person will receive an invitation email asking them to become a billing manager for your organization. Once the invited person clicks the accept link in their invitation email, they will automatically be added to the organization as a billing manager. If they don't already have a GitHub account, they will be directed to sign up for one, and they will be automatically added to the organization as a billing manager after they create an account.
The invited person will receive an invitation email asking them to become a billing manager for your organization. Once the invited person clicks the accept link in their invitation email, they will automatically be added to the organization as a billing manager. If they don't already have a {% data variables.product.prodname_dotcom %} account, they will be directed to sign up for one, and they will be automatically added to the organization as a billing manager after they create an account.

{% data reusables.organizations.billing-settings %}
1. Under "Billing management", next to "Billing managers", click **Add**.
Expand Down
2 changes: 1 addition & 1 deletion data/reusables/package_registry/authenticate-packages.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,4 +6,4 @@ You can use a {% data variables.product.pat_v1 %} to authenticate to {% data var

To authenticate to a {% data variables.product.prodname_registry %} registry within a {% data variables.product.prodname_actions %} workflow, you can use:
* `GITHUB_TOKEN` to publish packages associated with the workflow repository.
* A {% data variables.product.pat_v1 %} with at least `read:packages` scope to install packages associated with other private repositories (which `GITHUB_TOKEN` can't access).
* A {% data variables.product.pat_v1 %} with at least `read:packages` scope to install packages associated with other private repositories (`GITHUB_TOKEN` can be used if the repository is granted read access to the package. See [AUTOTITLE](/packages/learn-github-packages/configuring-a-packages-access-control-and-visibility)).
7 changes: 4 additions & 3 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading