Octomerger Bot
@@ -0,0 +1,104 @@
|
||||
---
|
||||
title: Connecting to a private network
|
||||
intro: 'You can connect {% data variables.product.prodname_dotcom %}-hosted runners to resources on a private network, including package registries, secret managers, and other on-premises services.'
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghec: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Actions
|
||||
- Developer
|
||||
---
|
||||
|
||||
{% data reusables.actions.enterprise-beta %}
|
||||
{% data reusables.actions.enterprise-github-hosted-runners %}
|
||||
|
||||
## About {% data variables.product.prodname_dotcom %}-hosted runners networking
|
||||
|
||||
By default, {% data variables.product.prodname_dotcom %}-hosted runners have access to the public internet. However, you may also want these runners to access resources on your private network, such as a package registry, a secret manager, or other on-premise services.
|
||||
|
||||
{% data variables.product.prodname_dotcom %}-hosted runners are shared across all {% data variables.product.prodname_dotcom %} customers, so you will need a way of connecting your private network to just your runners while they are running your workflows. There are a few different approaches you could take to configure this access, each with different advantages and disadvantages.
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.4 %}
|
||||
### Using an API Gateway with OIDC
|
||||
|
||||
With {% data variables.product.prodname_actions %}, you can use OpenID Connect (OIDC) tokens to authenticate your workflow outside of {% data variables.product.prodname_actions %}. For example, you could run an API Gateway on the edge of your private network that authenticates incoming requests with the OIDC token and then makes API requests on behalf of your workflow in your private network.
|
||||
|
||||
The following diagram gives an overview of this solution's architecture:
|
||||
|
||||
|
||||
|
||||
It's important that you authenticate not just that the OIDC token came from {% data variables.product.prodname_actions %}, but that it came specifically from your expected workflows, so that other {% data variables.product.prodname_actions %} users aren't able to access services in your private network. You can use OIDC claims to create these conditions. For more information, see "[Defining trust conditions on cloud roles using OIDC claims](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#defining-trust-conditions-on-cloud-roles-using-oidc-claims)."
|
||||
|
||||
The main disadvantage of this approach is you have to implement the API gateway to make requests on your behalf, as well as run it on the edge of your network.
|
||||
|
||||
But there are various advantages too:
|
||||
- You don't need to configure any firewalls, or modify the routing of your private network.
|
||||
- The API gateway is stateless, and so it scales horizontally to handle high availability and high throughput.
|
||||
|
||||
For more information, see [a reference implementation of an API Gateway](https://github.com/github/actions-oidc-gateway-example) (note that this requires customization for your use case and is not ready-to-run as-is), and "[About security hardening with OpenID Connect](/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)".
|
||||
{% endif %}
|
||||
|
||||
### Using WireGuard to create a network overlay
|
||||
|
||||
If you don't want to maintain separate infrastructure for an API Gateway, you can create an overlay network between your runner and a service in your private network, by running WireGuard in both places.
|
||||
|
||||
There are various disadvantages to this approach:
|
||||
|
||||
- To reach WireGuard running on your private service, you will need a well-known IP address and port that your workflow can reference: this can either be a public IP address and port, a port mapping on a network gateway, or a service that dynamically updates DNS.
|
||||
- WireGuard doesn't handle NAT traversal out of the box, so you'll need to identify a way to provide this service.
|
||||
- This connection is one-to-one, so if you need high availability or high throughput you'll need to build that on top of WireGuard.
|
||||
- You'll need to generate and securely store keys for both the runner and your private service. WireGuard uses UDP, so your network must support UDP traffic.
|
||||
|
||||
There are some advantages too, as you can run WireGuard on an existing server so you don't have to maintain separate infrastructure, and it's well supported on {% data variables.product.prodname_dotcom %}-hosted runners.
|
||||
|
||||
### Example: Configuring WireGuard
|
||||
|
||||
This example workflow configures WireGuard to connect to a private service.
|
||||
|
||||
For this example, the WireGuard instance running in the private network has this configuration:
|
||||
- Overlay network IP address of `192.168.1.1`
|
||||
- Public IP address and port of `1.2.3.4:56789`
|
||||
- Public key `examplepubkey1234...`
|
||||
|
||||
The WireGuard instance in the {% data variables.product.prodname_actions %} runner has this configuration:
|
||||
- Overlay network IP address of `192.168.1.2`
|
||||
- Private key stores as an {% data variables.product.prodname_actions %} secret under `WIREGUARD_PRIVATE_KEY`
|
||||
|
||||
```yaml
|
||||
name: WireGuard example
|
||||
|
||||
on:
|
||||
workflow_dispatch:
|
||||
|
||||
jobs:
|
||||
wireguard_example:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- run: sudo apt install wireguard
|
||||
|
||||
- run: echo "${{ secrets.WIREGUARD_PRIVATE_KEY }}" > privatekey
|
||||
|
||||
- run: sudo ip link add dev wg0 type wireguard
|
||||
|
||||
- run: sudo ip address add dev wg0 192.168.1.2 peer 192.168.1.1
|
||||
|
||||
- run: sudo wg set wg0 listen-port 48123 private-key privatekey peer examplepubkey1234... allowed-ips 0.0.0.0/0 endpoint 1.2.3.4:56789
|
||||
|
||||
- run: sudo ip link set up dev wg0
|
||||
|
||||
- run: curl -vvv http://192.168.1.1
|
||||
```
|
||||
|
||||
For more information, see [WireGuard's Quick Start](https://www.wireguard.com/quickstart/), as well as "[Encrypted Secrets](/actions/security-guides/encrypted-secrets)" for how to securely store keys.
|
||||
|
||||
### Using Tailscale to create a network overlay
|
||||
|
||||
Tailscale is a commercial product built on top of WireGuard. This option is very similar to WireGuard, except Tailscale is more of a complete product experience instead of an open source component.
|
||||
|
||||
It's disadvantages are similar to WireGuard: The connection is one-to-one, so you might need to do additional work for high availability or high throughput. You still need to generate and securely store keys. The protocol is still UDP, so your network must support UDP traffic.
|
||||
|
||||
However, there are some advantages over WireGuard: NAT traversal is built-in, so you don't need to expose a port to the public internet. It is by far the quickest of these options to get up and running, since Tailscale provides an {% data variables.product.prodname_actions %} workflow with a single step to connect to the overlay network.
|
||||
|
||||
For more information, see the [Tailscale GitHub Action](https://github.com/tailscale/github-action), as well as "[Encrypted Secrets](/actions/security-guides/encrypted-secrets)" for how to securely store keys.
|
||||
@@ -9,6 +9,7 @@ children:
|
||||
- /about-github-hosted-runners
|
||||
- /monitoring-your-current-jobs
|
||||
- /customizing-github-hosted-runners
|
||||
- /connecting-to-a-private-network
|
||||
shortTitle: Use GitHub-hosted runners
|
||||
---
|
||||
|
||||
|
||||
@@ -18,7 +18,9 @@ topics:
|
||||
shortTitle: Automatic user license sync
|
||||
---
|
||||
|
||||
## ライセンスの同期について
|
||||
## About automatic license synchronization
|
||||
|
||||
{% data reusables.enterprise-licensing.unique-user-licensing-model %}
|
||||
|
||||
{% data reusables.enterprise-licensing.about-license-sync %} 詳しい情報については「[{% data variables.product.prodname_github_connect %}にちて](/admin/configuration/configuring-github-connect/about-github-connect#data-transmission-for-github-connect)」を参照してください。
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
---
|
||||
title: Verifying or approving a domain for your enterprise
|
||||
title: Enterprise のドメインを検証または承認する
|
||||
shortTitle: ドメインの検証もしくは承認
|
||||
intro: 'You can verify your ownership of domains with {% data variables.product.company_short %} to confirm the identity of organizations owned by your enterprise account. You can also approve domains where organization members can receive email notifications.'
|
||||
product: '{% data reusables.gated-features.verify-and-approve-domain %}'
|
||||
@@ -30,7 +30,7 @@ redirect_from:
|
||||
|
||||
Enterprise アカウントのドメインの所有権を検証すると、プロファイルにドメインがリストされている各 Organization のプロファイルに「検証済み」のバッジが表示されます。 {% data reusables.organizations.verified-domains-details %}
|
||||
|
||||
Organization のオーナーは、検証済みのドメインにある各メンバーのメールアドレスを表示して Organization のメンバーのアイデンティティを確認できます。
|
||||
For domains configured at the enterprise level, enterprise owners can verify the identity of organization members by viewing each member's email address within the verified domain. Enterprise owners can also view a list of enterprise members who don't have an email address from a verified domain associated with their user account on {% data variables.product.prodname_dotcom %}. For more information, see "[Viewing members without an email address from a verified domain](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-without-an-email-address-from-a-verified-domain)."
|
||||
|
||||
Enterprise アカウントのドメインを検証した後、Enterprise アカウントが所有するすべての Organization の検証済みドメインにメール通知を制限できます。 For more information, see "[Restricting email notifications for your enterprise](/admin/policies/enforcing-policies-for-your-enterprise/restricting-email-notifications-for-your-enterprise)."
|
||||
|
||||
|
||||
@@ -107,6 +107,17 @@ If your enterprise uses {% data variables.product.prodname_emus %}, you can also
|
||||
|
||||
You can view a list of all dormant users {% ifversion ghes or ghae %} who have not been suspended and {% endif %}who are not site administrators. {% data reusables.enterprise-accounts.dormant-user-activity-threshold %} 詳細は「[休眠ユーザを管理する](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)」を参照してください。
|
||||
|
||||
{% ifversion ghec or ghes > 3.1 %}
|
||||
## Viewing members without an email address from a verified domain
|
||||
|
||||
You can view a list of members in your enterprise who don't have an email address from a verified domain associated with their user account on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.verified-domains-tab %}
|
||||
1. Under "Notification preferences", click the {% octicon "eye" aria-label="The github eye icon" %} **View enterprise members without an approved or verified domain email** link.
|
||||
{% endif %}
|
||||
|
||||
## 参考リンク
|
||||
|
||||
- 「[Enterprise のロール](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)」
|
||||
|
||||
@@ -43,11 +43,11 @@ topics:
|
||||
children:
|
||||
- /managing-your-github-billing-settings
|
||||
- /managing-billing-for-your-github-account
|
||||
- /managing-your-license-for-github-enterprise
|
||||
- /managing-licenses-for-visual-studio-subscriptions-with-github-enterprise
|
||||
- /managing-billing-for-github-actions
|
||||
- /managing-billing-for-github-codespaces
|
||||
- /managing-billing-for-github-packages
|
||||
- /managing-your-license-for-github-enterprise
|
||||
- /managing-licenses-for-visual-studio-subscriptions-with-github-enterprise
|
||||
- /managing-billing-for-github-advanced-security
|
||||
- /managing-billing-for-github-sponsors
|
||||
- /managing-billing-for-github-marketplace-apps
|
||||
|
||||
@@ -45,7 +45,7 @@ You can see your current usage in your [Azure account portal](https://portal.azu
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
{% data variables.product.company_short %} bills monthly for the total number of members in your enterprise account, as well as any additional services you use with {% data variables.product.prodname_ghe_cloud %}.
|
||||
{% data variables.product.company_short %} bills monthly for the total number of licensed seats for your organization or enterprise account, as well as any additional services you use with {% data variables.product.prodname_ghe_cloud %}, such as {% data variables.product.prodname_actions %} minutes. For more information about the licensed seats portion of your bill, see "[About per-user pricing](/billing/managing-billing-for-your-github-account/about-per-user-pricing)."
|
||||
|
||||
{% elsif ghes %}
|
||||
|
||||
@@ -64,40 +64,14 @@ Each user on {% data variables.product.product_location %} consumes a seat on yo
|
||||
Administrators for your enterprise account on {% data variables.product.prodname_dotcom_the_website %} can access and manage billing for the enterprise. For more information, see "[Roles in an enterprise]({% ifversion ghes %}/enterprise-cloud@latest{% endif %}/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise){% ifversion ghec %}."{% elsif ghes %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% endif %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
{% data reusables.enterprise-accounts.billing-microsoft-ea-overview %} For more information, see "[Connecting an Azure subscription to your enterprise](/billing/managing-billing-for-your-github-account/connecting-an-azure-subscription-to-your-enterprise)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
{% data reusables.billing.ghes-with-no-enterprise-account %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
## Per-user pricing
|
||||
|
||||
{% data variables.product.company_short %} bills for services consumed on {% data variables.product.prodname_dotcom_the_website %}, each user for deployments of {% data variables.product.prodname_ghe_server %}, and each member of organizations on {% data variables.product.prodname_ghe_cloud %}. For more information about per-user pricing, see "[About per-user pricing](/billing/managing-billing-for-your-github-account/about-per-user-pricing)."
|
||||
|
||||
{% data reusables.billing.per-user-pricing-reference %}
|
||||
|
||||
For more information about roles, see "[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)" or "[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
|
||||
|
||||
For more information about outside collaborators, see "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## About synchronization of license usage
|
||||
|
||||
{% data reusables.enterprise.about-deployment-methods %}
|
||||
|
||||
{% data reusables.enterprise-licensing.about-license-sync %} For more information, see {% ifversion ghec %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"{% ifversion ghec or ghes %}
|
||||
- "[About licenses for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)"{% endif %}
|
||||
- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: About per-user pricing
|
||||
intro: 'With per-user pricing, organizations {% ifversion ghec %}and enterprises {% endif %}pay based on team size to access advanced collaboration and management tools for teams, and optionally, security, compliance, and deployment controls.'
|
||||
title: ユーザごとの価格付けについて
|
||||
intro: '{% ifversion fpt or ghec %}For organizations{% ifversion ghec %} and enterprises{% endif %}, your {% else %}Your {% endif %}bill begins with the number of licensed seats you choose.'
|
||||
redirect_from:
|
||||
- /github/setting-up-and-managing-billing-and-payments-on-github/about-per-user-pricing
|
||||
- /articles/about-per-user-pricing
|
||||
@@ -8,6 +8,7 @@ redirect_from:
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
type: overview
|
||||
topics:
|
||||
- Downgrades
|
||||
@@ -16,69 +17,111 @@ topics:
|
||||
- Organizations
|
||||
---
|
||||
|
||||
## About per-user pricing
|
||||
|
||||
New organizations on {% data variables.product.prodname_dotcom_the_website %} can build public and open-source projects with {% data variables.product.prodname_free_team %}, or upgrade to a paid product with per-user pricing. For more information, see "[{% data variables.product.company_short %}'s products](/get-started/learning-about-github/githubs-products)" and "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)."
|
||||
|
||||
{% ifversion ghec %}Per-user pricing applies to all organizations that belong to your enterprise on {% data variables.product.prodname_dotcom_the_website %}, and to organizations using {% data variables.product.prodname_ghe_cloud %} that are not part of an enterprise. Each{% elsif fpt %}Per-user pricing means that each{% endif %} billing cycle, {% data variables.product.company_short %} charges for each member or outside collaborator within your organization{% ifversion ghec %} or enterprise{% endif %}. You also pay for each pending member or outside collaborator who has not yet accepted an invitation. {% data variables.product.company_short %} does not charge for members with the billing manager role{% ifversion ghec %}, or for enterprise owners who are not also a member of at least one organization in the enterprise{% endif %}. For more information, see {% ifversion ghec %}"[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)" or {% endif %}{% ifversion fpt or ghec %}"[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."{% endif %}
|
||||
|
||||
{% data variables.product.company_short %} counts each {% ifversion ghec %}member or {% endif %}outside collaborator once for billing purposes, even if the person has {% ifversion ghec %}membership in multiple organizations in an enterprise or {% endif %}access to multiple repositories owned by your organization.
|
||||
|
||||
For more information about outside collaborators, see "[Adding outside collaborators to repositories in your organization](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)."
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
If you deploy {% data variables.product.prodname_ghe_server %}, your usage includes licenses for each user on your instance. For more information about additional services and billing for {% data variables.product.prodname_ghe_cloud %}, see "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
|
||||
|
||||
{% elsif fpt %}
|
||||
|
||||
Organizations using a paid subscription before May 11, 2016 can choose to stay on their existing per-repository plan or switch to per-user pricing. {% data variables.product.company_short %} will notify you twelve months before any mandated change to your subscription. For more information on switching your subscription, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Overview of per-user pricing
|
||||
|
||||
{% data reusables.billing.per-user-pricing-reference %}
|
||||
|
||||
## About changes to your subscription
|
||||
## ユーザごとの価格付けについて
|
||||
|
||||
{% ifversion fpt %}
|
||||
{% data variables.product.prodname_dotcom_the_website %}上の新しいOrganizationは、{% data variables.product.prodname_free_team %}でパブリック及びオープンソースのプロジェクトを構築するか、ユーザごとの価格付けの有料製品にアップグレードすることができます。 詳しい情報については「[{% data variables.product.company_short %}の製品](/get-started/learning-about-github/githubs-products)」及び「[{% data variables.product.prodname_dotcom %}プランのアップグレード](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)」を参照してください。
|
||||
|
||||
You can change your {% data variables.product.prodname_dotcom %} subscription at any time.
|
||||
2016 年 5 月 11 日以前に有料プランを使っていた Organization は、既存のリポジトリ単位のプランに留まるか、ユーザごとの価格付けに切り替えることができます。 {% data variables.product.company_short %}は、プランへの強制的な変更の前に12ヶ月間通知します。 プランの切り替えに関する詳しい情報については、「[{% data variables.product.prodname_dotcom %} プランをアップグレードする](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)」を参照してください。
|
||||
|
||||
### About changes for organizations on per-user plans
|
||||
{% else %}
|
||||
|
||||
The foundation of your bill is the number of standard licensed seats that you choose for your{% ifversion ghec %} organization or{% endif %} enterprise.
|
||||
|
||||
{% data reusables.enterprise-licensing.unique-user-licensing-model %}
|
||||
|
||||
To ensure the same user isn't consuming more than one license for multiple enterprise deployments, you can synchronize license usage between your {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} environments. For more information, see "[About licenses for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)."
|
||||
|
||||
In addition to licensed seats, your bill may include other charges, such as {% data variables.product.prodname_GH_advanced_security %}. For more information, see "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)."
|
||||
{% endif %}
|
||||
|
||||
You can add more users to your organization{% ifversion ghec %} or enterprise at any time{% endif %}. If you pay for more users than are currently active, you can also reduce the number of paid users.{% ifversion fpt %} For more information, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)" and "[Downgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)."
|
||||
## People that consume a license
|
||||
|
||||
If you have questions about your subscription, contact {% data variables.contact.contact_support %}.
|
||||
Each person consumes one license, and {% data variables.product.company_short %} identifies individuals by primary email address.
|
||||
|
||||
To further support your team's collaboration abilities, you can upgrade to {% data variables.product.prodname_ghe_cloud %}, which includes features like SAML single sign-on and advanced auditing. {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
|
||||
For more information about per-user pricing for {% data variables.product.prodname_ghe_cloud %}, see [the {% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing).
|
||||
|
||||
{% elsif ghec %}
|
||||
|
||||
If you use an enterprise account on {% data variables.product.prodname_dotcom_the_website %} and have questions about changes to your subscription, contact {% data variables.contact.contact_enterprise_sales %}.
|
||||
|
||||
If you use an individual organization on {% data variables.product.prodname_ghe_cloud %}, you can upgrade or downgrade your subscription. For more information, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)" or "[Downgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)." If you have questions about your subscription, contact {% data variables.contact.contact_support %}.
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt %}
|
||||
|
||||
### About changes for organizations on per-repository plans
|
||||
|
||||
You can upgrade or downgrade between legacy paid plans in your organization's billing settings. When you upgrade to a plan with more private repositories, {% data variables.product.company_short %} immediately moves your account to your new plan and bills you for the difference in price, prorated for the number of days left in your billing cycle.
|
||||
|
||||
When you downgrade to a legacy paid plan with fewer private repositories, your new plan will take effect on your next billing date. If you have more private repositories than your new plan allows for, your private repositories will be locked when your new plan takes effect. To reduce your number of private repositories, you can make some of your private repositories public, or you can clone your private repositories locally and delete the copies on {% data variables.product.prodname_dotcom %}.
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
{% data variables.product.company_short %} bills for the following people.
|
||||
|
||||
{%- ifversion ghec %}
|
||||
- "[About enterprise accounts](/admin/overview/about-enterprise-accounts)"
|
||||
- Enterprise owners who are a member or owner of at least one organization in the enterprise
|
||||
{%- endif %}
|
||||
- "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)"
|
||||
- Organization members, including owners
|
||||
- Outside collaborators on private{% ifversion ghec %} or internal{% endif %} repositories owned by your organization, excluding forks
|
||||
- Anyone with a pending invitation to become an organization owner or member
|
||||
- Anyone with a pending invitation to become an outside collaborator on private{% ifversion ghec %} or internal{% endif %} repositories owned by your organization, excluding forks
|
||||
{%- ifversion ghec %}
|
||||
- Each user on any {% data variables.product.prodname_ghe_server %} instance that you deploy
|
||||
{%- endif %}
|
||||
- 休眠ユーザ
|
||||
|
||||
{% data variables.product.company_short %} does not bill for any of the following people.
|
||||
|
||||
{%- ifversion ghec %}
|
||||
- Enterprise owners who are not a member or owner of at least one organization in the enterprise
|
||||
- Enterprise billing managers
|
||||
{%- endif %}
|
||||
- Organization billing managers{% ifversion ghec %} for individual organizations on {% data variables.product.prodname_ghe_cloud %}{% endif %}
|
||||
- Anyone with a pending invitation to become an{% ifversion ghec %} enterprise or{% endif %} organization billing manager
|
||||
- Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization
|
||||
{%- ifversion ghes %}
|
||||
- 停止されたユーザ
|
||||
{%- endif %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**注釈**: {% data reusables.organizations.org-invite-scim %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
For more information, see {% ifversion not fpt %}"[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise)" or {% endif %}"[Roles in an organization](/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization)."
|
||||
|
||||
{% data variables.product.company_short %} counts each {% ifversion not fpt %}member or {% endif %}outside collaborator once for billing purposes, even if the user account has {% ifversion not fpt %}membership in multiple organizations in an enterprise or {% endif %}access to multiple repositories owned by your organization. 外部のコラボレータに関する詳しい情報については「[Organization内のリポジトリへの外部のコラボレータの追加](/organizations/managing-access-to-your-organizations-repositories/adding-outside-collaborators-to-repositories-in-your-organization)」を参照してください。
|
||||
|
||||
{% ifversion ghes %}Suspended users are not counted when calculating the number of licensed users consuming seats. For more information, see "[Suspending and unsuspending users](/admin/user-management/managing-users-in-your-enterprise/suspending-and-unsuspending-users)."{% endif %}
|
||||
|
||||
Dormant users do occupy a seat license.{% ifversion ghes %} As such, you can choose to suspend dormant users to release user licenses.{% endif %} For more information, see "[Managing dormant users](/admin/user-management/managing-users-in-your-enterprise/managing-dormant-users)."
|
||||
|
||||
## プランの変更について
|
||||
|
||||
{% ifversion fpt %}
|
||||
|
||||
{% data variables.product.prodname_dotcom %}プランは、いつでも変更できます。
|
||||
|
||||
### ユーザごとのプランのOrganizationでの変更について
|
||||
|
||||
{% endif %}
|
||||
|
||||
You can add more licensed seats to your {% ifversion fpt or ghec %} organization{% endif %}{% ifversion ghec %} or{% endif %}{% ifversion ghec or ghes %} enterprise{% endif %} at any time. If you pay for more seats than are being used, you can also reduce the number of seats.{% ifversion fpt %} For more information, see "[Upgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)" and "[Downgrading your {% data variables.product.prodname_dotcom %} subscription](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)."
|
||||
|
||||
プランに関する質問がある場合は、{% data variables.contact.contact_support %}にお問い合わせください。
|
||||
|
||||
Teamのコラボレーション機能をさらにサポートするために、SAMLシングルサインオンや高度な監査のような機能を含む{% data variables.product.prodname_ghe_cloud %}にアップグレードできます。 {% data reusables.enterprise.link-to-ghec-trial %}
|
||||
|
||||
{% data variables.product.prodname_ghe_cloud %}のユーザごとの価格付けに関する詳しい情報については[{% data variables.product.prodname_ghe_cloud %}ドキュメンテーション](/enterprise-cloud@latest/billing/managing-billing-for-your-github-account/about-per-user-pricing)を参照してください。
|
||||
|
||||
{% else %}
|
||||
|
||||
{% data variables.product.prodname_dotcom_the_website %}でEnterpriseアカウントを使用しており、プランの変更に関する疑問がある場合は、{% data variables.contact.contact_enterprise_sales %}にお問い合わせください。
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghec %}
|
||||
|
||||
{% data variables.product.prodname_ghe_cloud %}上の個々のOrganizationを使っている場合は、プランをアップグレードもしくはダウングレードできます。 詳しい情報については「[{% data variables.product.prodname_dotcom %}プランのアップグレード](/billing/managing-billing-for-your-github-account/upgrading-your-github-subscription)」もしくは「[{% data variables.product.prodname_dotcom %}プランのダウングレード](/billing/managing-billing-for-your-github-account/downgrading-your-github-subscription)」を参照してください。 プランに関する質問がある場合は、{% data variables.contact.contact_support %}にお問い合わせください。
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt %}
|
||||
|
||||
### リポジトリごとのプランのOrganizationの変更について
|
||||
|
||||
レガシーの有料プラン間でのアップグレード及びダウングレードは、Organizationの支払い設定から行えます。 より多くのプライベートリポジトリを持つプランにアップグレードするなら、{% data variables.product.company_short %}は即座にアカウントを新しいプランに移行し、支払いサイクル中に残っている日数に比例した価格の差異を課金します。
|
||||
|
||||
プライベートリポジトリ数が少ないレガシーの有料プランにダウングレードする場合、新しいプランは次の支払日に有効になります。 新しいプランで利用できる以上のプライベートリポジトリを持っている場合、新しいプランが有効になった時点でプライベートリポジトリはロックされます。 プライベートリポジトリの数を減らすには、プライベートリポジトリの一部をパブリックにするか、プライベートリポジトリをローカルにクローンして {% data variables.product.prodname_dotcom %} 上のコピーを削除します。
|
||||
|
||||
{% endif %}
|
||||
|
||||
## 参考リンク
|
||||
|
||||
{%- ifversion not fpt %}
|
||||
- 「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」
|
||||
{%- endif %}
|
||||
- 「[リポジトリについて](/repositories/creating-and-managing-repositories/about-repositories#about-repository-visibility)」
|
||||
|
||||
@@ -20,8 +20,8 @@ versions:
|
||||
ghae: '*'
|
||||
children:
|
||||
- /about-billing-for-github-accounts
|
||||
- /about-per-user-pricing
|
||||
- /about-billing-for-your-enterprise
|
||||
- /about-per-user-pricing
|
||||
- /viewing-the-subscription-and-usage-for-your-enterprise-account
|
||||
- /upgrading-your-github-subscription
|
||||
- /viewing-and-managing-pending-changes-to-your-subscription
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: About licenses for GitHub Enterprise
|
||||
intro: '{% ifversion ghec %}If you deploy {% data variables.product.prodname_ghe_server %} in addition to using {% data variables.product.prodname_ghe_cloud %}, each{% elsif ghes %}Each{% endif %} {% data variables.product.prodname_ghe_server %} instance requires a license file to validate and unlock the application.'
|
||||
intro: '{% ifversion ghec %}If you deploy {% data variables.product.prodname_ghe_server %} in addition to using {% data variables.product.prodname_ghe_cloud %}, you{% else %}You{% endif %} can synchronize your license usage between{% ifversion ghes %} {% data variables.product.prodname_enterprise %}{% endif %} deployments, and use a license file to unlock each {% data variables.product.prodname_ghe_server %} instance.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
@@ -11,32 +11,32 @@ topics:
|
||||
shortTitle: About licenses
|
||||
---
|
||||
|
||||
## About license files for {% data variables.product.prodname_enterprise %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
## About licensing for {% data variables.product.prodname_enterprise %}
|
||||
|
||||
{% data reusables.enterprise.about-deployment-methods %}
|
||||
|
||||
{% endif %}
|
||||
{% data reusables.enterprise-licensing.unique-user-licensing-model %}
|
||||
|
||||
To ensure the same user isn't consuming more than one license for multiple enterprise deployments, you can synchronize license usage between your {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} deployments.
|
||||
|
||||
In order to use a {% data variables.product.prodname_ghe_server %} instance, you must upload a license file that {% data variables.product.company_short %} provides when you purchase, renew, or add user licenses to {% data variables.product.prodname_enterprise %}.
|
||||
|
||||
## About synchronization of license usage for {% data variables.product.prodname_enterprise %}
|
||||
|
||||
{% data reusables.enterprise-licensing.about-license-sync %} For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."
|
||||
|
||||
## About license files for {% data variables.product.prodname_enterprise %}
|
||||
|
||||
When you purchase or renew {% data variables.product.prodname_enterprise %}, {% data variables.product.company_short %} provides a license file {% ifversion ghec %}for your deployments of {% data variables.product.prodname_ghe_server %}{% elsif ghes %}for {% data variables.product.product_location_enterprise %}{% endif %}. A license file has an expiration date and controls the number of people who can use {% data variables.product.product_location_enterprise %}. After you download and install {% data variables.product.prodname_ghe_server %}, you must upload the license file to unlock the application for you to use.
|
||||
|
||||
For more information about downloading your license file, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)." For more information about uploading your license file, see {% ifversion ghec %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %}
|
||||
For more information about downloading your license file, see "[Downloading your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise)."
|
||||
|
||||
For more information about uploading your license file, see {% ifversion ghec %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Uploading a new license to {% data variables.product.prodname_ghe_server %}](/billing/managing-your-license-for-github-enterprise/uploading-a-new-license-to-github-enterprise-server)."{% endif %}
|
||||
|
||||
If your license expires, you won't be able to access {% data variables.product.prodname_ghe_server %} via a web browser or Git. If needed, you will be able to use command-line utilities to back up all your data. For more information, see {% ifversion ghec %}"[Configuring backups on your appliance]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/guides/installation/configuring-backups-on-your-appliance)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Configuring backups on your appliance](/admin/guides/installation/configuring-backups-on-your-appliance)." {% endif %}
|
||||
|
||||
If you have any questions about renewing your license, contact {% data variables.contact.contact_enterprise_sales %}.
|
||||
|
||||
## About synchronization of license usage for {% data variables.product.prodname_enterprise %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
{% data reusables.enterprise.about-deployment-methods %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.enterprise-licensing.about-license-sync %} For more information, see {% ifversion ghec %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/enterprise-server/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}"[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About billing for your enterprise](/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise)"
|
||||
|
||||
@@ -23,5 +23,6 @@ children:
|
||||
- /uploading-a-new-license-to-github-enterprise-server
|
||||
- /viewing-license-usage-for-github-enterprise
|
||||
- /syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud
|
||||
- /troubleshooting-license-usage-for-github-enterprise
|
||||
---
|
||||
|
||||
|
||||
@@ -14,6 +14,8 @@ shortTitle: Sync license usage
|
||||
|
||||
## About synchronization of license usage
|
||||
|
||||
{% data reusables.enterprise-licensing.unique-user-licensing-model %}
|
||||
|
||||
{% data reusables.enterprise-licensing.about-license-sync %}
|
||||
|
||||
To ensure that you see up-to-date license details on {% data variables.product.prodname_dotcom_the_website %}, you can sync license usage between the environments automatically, using {% data variables.product.prodname_github_connect %}. For more information about {% data variables.product.prodname_github_connect %}, see "[About {% data variables.product.prodname_github_connect %}]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/about-github-connect){% ifversion ghec %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}."{% endif %}
|
||||
|
||||
@@ -0,0 +1,90 @@
|
||||
---
|
||||
title: Troubleshooting license usage for GitHub Enterprise
|
||||
intro: You can troubleshoot license usage for your enterprise by auditing license reports.
|
||||
permissions: 'Enterprise owners can review license usage for {% data variables.product.prodname_enterprise %}.'
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
type: how_to
|
||||
topics:
|
||||
- Enterprise
|
||||
- Licensing
|
||||
shortTitle: Troubleshoot license usage
|
||||
---
|
||||
|
||||
## About unexpected license usage
|
||||
|
||||
If the number of consumed licenses for your enterprise is unexpected, you can review your consumed license report to audit your license usage across all your enterprise deployments and subscriptions. If you find errors, you can try troubleshooting steps. For more information about viewing your license usage, see "[Viewing license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" and "[Viewing the subscription and usage for your enterprise account](/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account)."
|
||||
|
||||
For privacy reasons, enterprise owners cannot directly access the details of user accounts.
|
||||
|
||||
## About the calculation of consumed licenses
|
||||
|
||||
{% data variables.product.company_short %} bills for each person who uses deployments of {% data variables.product.prodname_ghe_server %}, is a member of an organization on {% data variables.product.prodname_ghe_cloud %}, or is a {% data variables.product.prodname_vs_subscriber %}. For more information about the people in your enterprise who are counted as consuming a license, see "[About per-user pricing](/billing/managing-billing-for-your-github-account/about-per-user-pricing)."
|
||||
|
||||
{% data reusables.enterprise-licensing.about-license-sync %}
|
||||
|
||||
## Fields in the consumed license files
|
||||
|
||||
The {% data variables.product.prodname_dotcom_the_website %} license usage report and {% data variables.product.prodname_ghe_server %} exported license usage file include a variety of fields to help you troubleshoot license usage for your enterprise.
|
||||
### {% data variables.product.prodname_dotcom_the_website %} license usage report (CSV file)
|
||||
|
||||
The license usage report for your enterprise is a CSV file that contains the following information about members of your enterprise. Some fields are specific to your {% data variables.product.prodname_ghe_cloud %} (GHEC) deployment, {% data variables.product.prodname_ghe_server %} (GHES) connected environments, or your {% data variables.product.prodname_vs %} subscriptions (VSS) with GitHub Enterprise.
|
||||
|
||||
| フィールド | 説明 |
|
||||
| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| 名前 | First and last name for the user's account on GHEC. |
|
||||
| Handle or email | GHEC username, or the email address associated with the user's account on GHES. |
|
||||
| Profile link | Link to the {% data variables.product.prodname_dotcom_the_website %} profile page for the user's account on GHEC. |
|
||||
| License type | Can be one of: `Visual Studio subscription` or `Enterprise`. |
|
||||
| License status | Identifies if a user account on {% data variables.product.prodname_dotcom_the_website %} successfully matched either a {% data variables.product.prodname_vs_subscriber %} or GHES user.<br><br>Can be one of: `Matched`, `Pending Invitation`, `Server Only`, blank. |
|
||||
| Member roles | For each of the organizations the user belongs to on GHEC, the organization name and the person's role in that organization (`Owner` or `Member`) separated by a colon<br><br>Each organization is delimited by a comma. |
|
||||
| Enterprise role | Can be one of: `Owner` or `Member`. |
|
||||
|
||||
{% data variables.product.prodname_vs_subscriber %}s who are not yet members of at least one organization in your enterprise will be included in the report with a pending invitation status, and will be missing values for the "Name" or "Profile link" field.
|
||||
|
||||
### {% data variables.product.prodname_ghe_server %} exported license usage (JSON file)
|
||||
|
||||
Your {% data variables.product.prodname_ghe_server %} license usage is a JSON file that is typically used when performing a manual sync of user licenses between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} deployments. The file contains the following information specific to your {% data variables.product.prodname_ghe_server %} environment.
|
||||
|
||||
| フィールド | 説明 |
|
||||
| ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| 機能 | The {% data variables.product.prodname_github_connect %} features that are enabled on your {% data variables.product.prodname_ghe_server %} instance, and the date and time of enablement. |
|
||||
| Host name | The hostname of your {% data variables.product.prodname_ghe_server %} instance. |
|
||||
| HTTP only | Whether Transport Layer Security (TLS) is enabled and configured on your {% data variables.product.prodname_ghe_server %} instance. Can be one of: `True` or `False`. |
|
||||
| ライセンス | {% data variables.product.prodname_ghe_server %} ライセンスのハッシュ. |
|
||||
| Public key | {% data variables.product.prodname_ghe_server %} ライセンスの公開鍵の部分. |
|
||||
| Server ID | UUID generated for your {% data variables.product.prodname_ghe_server %} instance. |
|
||||
| バージョン | The version of your {% data variables.product.prodname_ghe_server %} instance. |
|
||||
|
||||
## Troubleshooting consumed licenses
|
||||
|
||||
If the number of consumed seats is unexpected, or if you've recently removed members from your enterprise, we recommend that you audit your license usage.
|
||||
|
||||
To determine which users are currently consuming seat licenses, first try reviewing the consumed licenses report for your enterprise{% ifversion ghes %} and/or an export of your {% data variables.product.prodname_ghe_server %} license usage{% endif %} for unexpected entries.
|
||||
|
||||
There are two especially common reasons for inaccurate or incorrect license seat counts.
|
||||
- The email addresses associated with a user do not match across your enterprise deployments and subscriptions.
|
||||
- An email address for a user was recently updated or verified to correct a mismatch, but a license sync job hasn't run since the update was made.
|
||||
|
||||
When attempting to match users across enterprises, {% data variables.product.company_short %} identifies individuals by the verified email addresses associated with their {% data variables.product.prodname_dotcom_the_website %} account, and the primary email address associated with their {% data variables.product.prodname_ghe_server %} account and/or the email address assigned to the {% data variables.product.prodname_vs_subscriber %}.
|
||||
|
||||
Your license usage is recalculated shortly after each license sync is performed. You can view the timestamp of the last license sync job, and, if a job hasn't run since an email address was updated or verified, to resolve an issue with your consumed license report you can manually trigger one. For more information, see "[Syncing license usage between GitHub Enterprise Server and GitHub Enterprise Cloud](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."
|
||||
|
||||
{% ifversion ghec or ghes > 3.1 %}
|
||||
If your enterprise uses verified domains, review the list of enterprise members who do not have an email address from a verified domain associated with their {% data variables.product.prodname_dotcom_the_website %} account. Often, these are the users who erroneously consume more than one licensed seat. For more information, see "[Viewing members without an email address from a verified domain](/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise#viewing-members-without-an-email-address-from-a-verified-domain)."
|
||||
{% endif %}
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** For privacy reasons, your consumed license report only includes the email address associated with a user account on {% data variables.product.prodname_dotcom_the_website %} if the address is hosted by a verified domain. For this reason, we recommend using verified domains with your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. Then, if one person is erroneously consuming multiple licenses, you can more easily troubleshoot, as you will have access to the email address that is being used for license deduplication.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
If your license includes {% data variables.product.prodname_vss_ghe %} and your enterprise also includes at least one {% data variables.product.prodname_ghe_server %} connected environment, we strongly recommend using {% data variables.product.prodname_github_connect %} to automatically synchronize your license usage. For more information, see "[About Visual Studio subscriptions with GitHub Enterprise](/enterprise-cloud@latest/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
If you still have questions about your consumed licenses after reviewing the troubleshooting information above, you can contact {% data variables.contact.github_support %} through the {% data variables.contact.contact_enterprise_portal %}.
|
||||
@@ -24,15 +24,15 @@ You can view license usage for your enterprise account on {% data variables.prod
|
||||
|
||||
You can view license usage for {% data variables.product.prodname_ghe_server %} on {% data variables.product.product_location %}.
|
||||
|
||||
{% data reusables.enterprise-licensing.you-can-sync-for-a-combined-view %} For more information about the display of license usage on {% data variables.product.prodname_dotcom_the_website %}, see "[Viewing license usage for {% data variables.product.prodname_enterprise %}](/enterprise-cloud@latest/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
|
||||
{% data reusables.enterprise-licensing.you-can-sync-for-a-combined-view %} For more information about the display of license usage on {% data variables.product.prodname_dotcom_the_website %} and identifying when the last license sync occurred, see "[Viewing license usage for {% data variables.product.prodname_enterprise %}](/enterprise-cloud@latest/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise)" in the {% data variables.product.prodname_ghe_cloud %} documentation.
|
||||
|
||||
To learn more about the license data associated with your enterprise account and how the number of consumed user seats are calculated, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)."
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Viewing license usage on {% ifversion ghec %}{% data variables.product.prodname_dotcom_the_website %}{% elsif ghes %}{% data variables.product.product_location %}{% endif %}
|
||||
|
||||
You can view the license usage for your enterprise and download a file with license details.
|
||||
|
||||
{% data reusables.billing.license-statuses %}
|
||||
You can view the license usage for your enterprise and download a file with license details. If you're not seeing expected license counts in this report, it's possible that the subscriber’s assigned {% data variables.product.prodname_vs %} subscription email address and {% data variables.product.prodname_dotcom_the_website %} email address aren't exactly the same. For further information, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)."
|
||||
|
||||
{% ifversion ghec %}
|
||||
|
||||
@@ -41,6 +41,7 @@ You can view the license usage for your enterprise and download a file with lice
|
||||
1. In the left sidebar, click **Enterprise licensing**.
|
||||
|
||||
1. Review your current {% data variables.product.prodname_enterprise %} license, as well as consumed and available user licenses.
|
||||
- To download the consumed license report as a CSV file, in the top right, click {% octicon "download" aria-label="The download icon" %}. For more information about reviewing the data in this report, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)."
|
||||
- If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use. For more information, see "[Viewing your {% data variables.product.prodname_GH_advanced_security %} usage](/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage)."
|
||||
|
||||
{% elsif ghes %}
|
||||
@@ -49,6 +50,20 @@ You can view the license usage for your enterprise and download a file with lice
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
{% data reusables.enterprise-accounts.license-tab %}
|
||||
1. Review your current {% data variables.product.prodname_enterprise %} license, as well as consumed and available user licenses.{% ifversion ghes %}
|
||||
- To download the consumed license report as a JSON file, in the top right under "Quick links", choose **Export license usage**. For more information about reviewing the data in this report, see "[Troubleshooting license usage for GitHub Enterprise](/billing/managing-your-license-for-github-enterprise/troubleshooting-license-usage-for-github-enterprise)."
|
||||
- If your license includes {% data variables.product.prodname_GH_advanced_security %}, you can review your total seat use as well as a per-organization breakdown of committers. For more information, see "[Managing {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security)."{% endif %}
|
||||
|
||||
{% endif %}
|
||||
{% ifversion ghec %}
|
||||
## Viewing the last license sync date
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise-on-dotcom %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
1. In the left sidebar, click **Enterprise licensing**.
|
||||
|
||||
1. To identify when the last license sync occurred, under "Enterprise Server instances", look for timestamps next to usage uploaded or synced events.
|
||||
- "Server usage uploaded" indicates license usage between environments was manually updated when a {% data variables.product.prodname_ghe_server %} license file was uploaded.
|
||||
- "{% data variables.product.prodname_github_connect %} server usage synced" indicates license usage between environments was automatically updated.
|
||||
- "{% data variables.product.prodname_github_connect %} server usage never synced" indicates that {% data variables.product.prodname_github_connect %} is configured, but license usage between environments has never updated successfully.
|
||||
|
||||
{% endif %}
|
||||
|
||||
@@ -269,14 +269,14 @@ on:
|
||||
この種のマージコミットは{% data variables.product.prodname_dependabot %}によって作成されるので、このコミットで実行されるワークフローは読み取りのみの権限を持つことになります。 {% data variables.product.prodname_code_scanning %}と{% data variables.product.prodname_dependabot %}のセキュリティ更新またはバージョン更新をリポジトリで有効化した場合は、{% data variables.product.prodname_dependabot %}の`@dependabot squash and merge`コマンドは使わないことをおすすめします。 その代わりに、リポジトリで自動マージを有効化できます。 これは、すべての必須レビューが満たされ、ステータスチェックをパスしたら、Pyll Requestは自動的にマージされるということです。 自動マージの有効化に関する詳しい情報については「[Pull Requestの自動マージ](/github/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request#enabling-auto-merge)」を参照してください。
|
||||
{% endif %}
|
||||
|
||||
## Error: "is not a .ql file, .qls file, a directory, or a query pack specification"
|
||||
## エラー: "is not a .ql file, .qls file, a directory, or a query pack specification"
|
||||
|
||||
You will see this error if CodeQL is unable to find the named query, query suite, or query pack at the location requested in the workflow. There are two common reasons for this error.
|
||||
CodeQLが名前付きクエリ、クエリスイート、あるいはクエリパックをワークフロー中のリクエストされた場所で見つけられなかった場合、このエラーが表示されます。 このエラーには、2つの一般的な原因があります。
|
||||
|
||||
- There is a typo in the workflow.
|
||||
- A resource the workflow refers to by path was renamed, deleted, or moved to a new location.
|
||||
- ワークフロー中にタイプミスがある。
|
||||
- ワークフローがパスで参照しているリソースの名前が変更されたり、削除されたり、新しい場所に移動されたりしている。
|
||||
|
||||
After verifying the location of the resource, you can update the workflow to specify the correct location. If you run additional queries in Go analysis, you may have been affected by the relocation of the source files. For more information, see [Relocation announcement: `github/codeql-go` moving into `github/codeql`](https://github.com/github/codeql-go/issues/741) in the github/codeql-go repository.
|
||||
リソースの場所を確認したあと、ワークフローを更新して正しい場所を指定できます。 Goの分析で追加のクエリを実行する場合、ソースファイルの移動の影響を受けているかもしれません。 詳しい情報については、github/codeql-goリポジトリの[場所の移動のお知らせ:`github/codeql-go`は`github/codeql`に移動しました](https://github.com/github/codeql-go/issues/741)を参照してください。
|
||||
|
||||
## Warning: "git checkout HEAD^2 is no longer necessary"
|
||||
|
||||
|
||||
@@ -73,6 +73,31 @@ You can also enable or disable {% data variables.product.prodname_dependabot_sec
|
||||
1. Under "Code security and analysis", to the right of "{% data variables.product.prodname_dependabot %} security updates", click **Enable** to enable the feature or **Disable** to disable it. {% ifversion fpt or ghec %}For public repositories, the button is disabled if the feature is always enabled.{% endif %}
|
||||
{% ifversion fpt or ghec %}{% else %}{% endif %}
|
||||
|
||||
## Overriding the default behavior with a configuration file
|
||||
|
||||
You can override the default behavior of {% data variables.product.prodname_dependabot_security_updates %} by adding a dependabot.yml file to your repository. For more information, see "[Configuration options for the dependabot.yml file](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file)."
|
||||
|
||||
If you only require security updates and want to exclude version updates, you can set `open-pull-request-limit` to `0` in order to prevent version updates for a given `package-ecosystem`. For more information, see "[`open-pull-request-limit`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#open-pull-requests-limit)."
|
||||
|
||||
```
|
||||
# Example configuration file that:
|
||||
# - Ignores lodash dependency
|
||||
# - Disables version-updates
|
||||
|
||||
version: 2
|
||||
updates:
|
||||
- package-ecosystem: "npm"
|
||||
directory: "/"
|
||||
schedule:
|
||||
interval: "daily"
|
||||
ignore:
|
||||
- dependency-name: "lodash"
|
||||
# For Lodash, ignore all updates
|
||||
# Disable version updates for npm dependencies
|
||||
open-pull-requests-limit: 0
|
||||
```
|
||||
|
||||
For more information about the configuration options available for security updates, see the table in "[Configuration options for the dependabot.yml file](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#configuration-options-for-the-dependabotyml-file)."
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -35,35 +35,11 @@ shortTitle: dependabot.ymlの設定
|
||||
|
||||
*dependabot.yml* ファイルには、必須の最上位キーに `version` と `updates` の 2 つがあります。 あるいは、トップレベルの`registries`キー{% ifversion fpt or ghec or ghes > 3.4 %}や`enable-beta-ecosystems`キー{% endif %}を含めることができます。 ファイルは、`version: 2` で始まる必要があります。
|
||||
|
||||
## 更新の設定オプション
|
||||
## Configuration options for the *dependabot.yml* file
|
||||
|
||||
最上位の `updates` キーは必須です。 これを使用することで、{% data variables.product.prodname_dependabot %} がバージョンやプロジェクトの依存性を更新する方法を設定できます。 各エントリは、特定のパッケージマネージャーの更新設定を行います。 次のオプションを使用できます。
|
||||
|
||||
| オプション | 必須 | 説明 |
|
||||
|:-------------------------------------------------------------------------- |:-----:|:----------------------------------------------------------------------- |
|
||||
| [`package-ecosystem`](#package-ecosystem) | **X** | 使用するパッケージマネージャー |
|
||||
| [`directory`](#directory) | **X** | パッケージマニフェストの場所 |
|
||||
| [`schedule.interval`](#scheduleinterval) | **X** | 更新を確認する頻度 |
|
||||
| [`allow`](#allow) | | 許可する更新をカスタマイズする |
|
||||
| [`assignees`](#assignees) | | プルリクエストのアサイン担当者 |
|
||||
| [`commit-message`](#commit-message) | | コミットメッセージの設定 |{% ifversion fpt or ghec or ghes > 3.4 %}
|
||||
| [`enable-beta-ecosystems`](#enable-beta-ecosystems) | | ベータレベルのサポートがあるエコシステムを有効にする
|
||||
{% endif %}
|
||||
| [`ignore`](#ignore) | | 特定の依存関係またはバージョンを無視する |
|
||||
| [`insecure-external-code-execution`](#insecure-external-code-execution) | | マニフェストファイル内でコードの実行を許可または拒否する |
|
||||
| [`labels`](#labels) | | プルリクエストに設定するラベル |
|
||||
| [`マイルストーン`](#milestone) | | プルリクエストに設定するマイルストーン |
|
||||
| [`open-pull-requests-limit`](#open-pull-requests-limit) | | バージョン更新時のオープンなプルリクエスト数を制限する |
|
||||
| [`pull-request-branch-name.separator`](#pull-request-branch-nameseparator) | | プルリクエストブランチ名の区切り文字を変更する |
|
||||
| [`rebase-strategy`](#rebase-strategy) | | 自動リベースを無効にする |
|
||||
| [`registries`](#registries) | | {% data variables.product.prodname_dependabot %} がアクセスできるプライベートリポジトリ |
|
||||
| [`レビュー担当者`](#reviewers) | | プルリクエストのレビュー担当者 |
|
||||
| [`schedule.day`](#scheduleday) | | 更新を確認する曜日 |
|
||||
| [`schedule.time`](#scheduletime) | | 更新を確認する時刻 (hh:mm) |
|
||||
| [`schedule.timezone`](#scheduletimezone) | | 時刻のタイムゾーン（ゾーン識別子） |
|
||||
| [`target-branch`](#target-branch) | | プルリクエストを作成するブランチ |
|
||||
| [`vendor`](#vendor) | | ベンダーまたはキャッシュされた依存関係を更新する |
|
||||
| [`versioning-strategy`](#versioning-strategy) | | マニフェストのバージョン要件の更新方法 |
|
||||
{% data reusables.dependabot.configuration-options %}
|
||||
|
||||
これらのオプションは、次のようなカテゴリに幅広く適合しています。
|
||||
|
||||
@@ -81,7 +57,7 @@ shortTitle: dependabot.ymlの設定
|
||||
|
||||
脆弱性のあるパッケージマニフェストのセキュリティアップデートは、デフォルトブランチでのみ発生します。 設定オプションが同じブランチに設定され（`target-branch` を使用しない場合は true）、脆弱性のあるマニフェストの `package-ecosystem` と `directory` を指定している場合、セキュリティアップデートのプルリクエストで関連オプションが使用されます。
|
||||
|
||||
一般に、セキュリティアップデートでは、メタデータの追加や動作の変更など、プルリクエストに影響する設定オプションが使用されます。 セキュリティアップデートに関する詳しい情報については、「[{% data variables.product.prodname_dependabot_security_updates %} を設定する](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)」を参照してください。
|
||||
一般に、セキュリティアップデートでは、メタデータの追加や動作の変更など、プルリクエストに影響する設定オプションが使用されます。 For more information about security updates, see "[Configuring {% data variables.product.prodname_dependabot_security_updates %}](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-dependabot-security-updates)."
|
||||
|
||||
{% endnote %}
|
||||
|
||||
@@ -316,7 +292,7 @@ updates:
|
||||
|
||||
リポジトリが`ignore`の設定を保存したかは、リポジトリで`"@dependabot ignore" in:comments`を検索すれば調べられます。 この方法で無視された依存関係の無視を解除したいなら、Pull Requestを再度オープンしてください。
|
||||
|
||||
`@dependabot ignore` コマンドに関する詳細については、「[依存関係の更新に関するプルリクエストを管理する](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)」をご覧ください。
|
||||
For more information about the `@dependabot ignore` commands, see "[Managing pull requests for dependency updates](/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/managing-pull-requests-for-dependency-updates#managing-dependabot-pull-requests-with-comment-commands)."
|
||||
|
||||
#### 無視する依存関係とバージョンを指定する
|
||||
|
||||
|
||||
@@ -84,6 +84,12 @@ The {% data variables.product.prodname_dependabot_alerts %} count in {% data var
|
||||
**Check**: If there is a discrepancy in the totals you are seeing, check that you are not comparing alert numbers with dependency numbers. Also check that you are viewing all alerts and not a subset of filtered alerts.
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.2 %}
|
||||
## Can Dependabot ignore specific dependencies?
|
||||
|
||||
You can configure {% data variables.product.prodname_dependabot %} to ignore specific dependencies in the configuration file, which will prevent security and version updates for those dependencies. If you only wish to use security updates, you will need to override the default behavior with a configuration file. For more information, see "[Overriding the default behavior with a configuration file](/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates#overriding-the-default-behavior-with-a-configuration-file)" to prevent version updates from being activated. For information about ignoring dependencies, see "[`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore)."
|
||||
{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About {% data variables.product.prodname_dependabot_alerts %}](/code-security/supply-chain-security/about-alerts-for-vulnerable-dependencies)"
|
||||
|
||||
@@ -116,8 +116,10 @@ There are two types of {% data variables.product.prodname_dependabot_updates %}:
|
||||
- Triggered by a {% data variables.product.prodname_dependabot %} alert
|
||||
- Update dependencies to the minimum version that resolves a known vulnerability
|
||||
- Supported for ecosystems the dependency graph supports
|
||||
- Does not require a configuration file, but you can use one to override the default behavior
|
||||
|
||||
{% data variables.product.prodname_dependabot_version_updates %}:
|
||||
- Requires a configuration file
|
||||
- Run on a schedule you configure
|
||||
- Update dependencies to the latest version that matches the configuration
|
||||
- Supported for a different group of ecosystems
|
||||
|
||||
@@ -32,7 +32,7 @@ To read about how GitHub is used by educators, see [GitHub Education stories](ht
|
||||
- New organizations in your enterprise are automatically added to your enterprise account. To add organizations that existed before your school joined the {% data variables.product.prodname_campus_program %}, please contact [GitHub Education Support](https://support.github.com/contact/education). For more information about administrating your enterprise, see the [enterprise administrators documentation](/admin). New organizations in your enterprise are automatically added to your enterprise account. To add organizations that existed before your school joined the {% data variables.product.prodname_campus_program %}, please contact GitHub Education Support.
|
||||
|
||||
|
||||
To read more about {% data variables.product.prodname_dotcom %}'s privacy practices, see ["Global Privacy Practices"](/github/site-policy/global-privacy-practices).
|
||||
To read more about {% data variables.product.prodname_dotcom %}'s privacy practices, see "[Global Privacy Practices](/github/site-policy/global-privacy-practices)."
|
||||
|
||||
## {% data variables.product.prodname_campus_program %} Application Eligibility
|
||||
|
||||
|
||||
@@ -27,7 +27,7 @@ If you'd like to match the commits in your repository to the authors' GitHub per
|
||||
3. Choose your personal account or an organization to own the repository, then type a name for the repository on GitHub. ![リポジトリの [Owner] メニューと、リポジトリ名フィールド](/assets/images/help/importer/import-repo-owner-name.png)
|
||||
4. 新しいリポジトリを*パブリック*にするか*プライベート*にするかを指定します。 詳細は「[リポジトリの可視性を設定する](/articles/setting-repository-visibility)」を参照してください。 ![リポジトリの [Public] と [Private] を選択するラジオ ボタン](/assets/images/help/importer/import-public-or-private.png)
|
||||
5. 入力した情報を確認し、[**Begin import**] をクリックします。 ![[Begin import] ボタン](/assets/images/help/importer/begin-import-button.png)
|
||||
6. 既存のプロジェクトがパスワードで保護されている場合は、必要なログイン情報を入力して [**Submit**] をクリックします。 ![パスワード保護されているプロジェクトのパスワード入力フォームと [Submit] ボタン](/assets/images/help/importer/submit-old-credentials-importer.png)
|
||||
6. If your old project requires credentials, type your login information for that project, then click **Submit**. If SAML SSO or 2FA are enabled for your user account on the old project, enter a personal access token with repository read permissions in the "Password" field instead of your password. ![パスワード保護されているプロジェクトのパスワード入力フォームと [Submit] ボタン](/assets/images/help/importer/submit-old-credentials-importer.png)
|
||||
7. 既存のプロジェクトのクローン URL で複数のプロジェクトがホストされいる場合は、インポートしたいプロジェクトを選択して [**Submit**] をクリックします。 ![インポートするプロジェクトのリストと [Submit] ボタン](/assets/images/help/importer/choose-project-importer.png)
|
||||
8. プロジェクトに 100 MB を超えるファイルがある場合は、[Git Large File Storage](/articles/versioning-large-files) を使用して大きいファイルをインポートするかどうかを選択し、[**Continue**] をクリックします。 ![[Git Large File Storage] メニューと [Continue] ボタン](/assets/images/help/importer/select-gitlfs-importer.png)
|
||||
|
||||
|
||||
@@ -6,6 +6,5 @@ versions:
|
||||
children:
|
||||
- /about-github-copilot-telemetry
|
||||
- /github-copilot-telemetry-terms
|
||||
- /research-recitation
|
||||
---
|
||||
|
||||
|
||||
@@ -1,141 +0,0 @@
|
||||
---
|
||||
title: Research recitation
|
||||
intro: 'A first look at rote learning in {% data variables.product.prodname_dotcom %} Copilot suggestions.'
|
||||
redirect_from:
|
||||
- /early-access/github/copilot/research-recitation
|
||||
versions:
|
||||
fpt: '*'
|
||||
---
|
||||
|
||||
By: Albert Ziegler (@wunderalbert)
|
||||
|
||||
## {% data variables.product.prodname_dotcom %} Copilot: Parrot or Crow?
|
||||
A first look at rote learning in {% data variables.product.prodname_dotcom %} Copilot suggestions.
|
||||
|
||||
## はじめに
|
||||
|
||||
{% data variables.product.prodname_dotcom %} Copilot is trained on billions of lines of public code. The suggestions it makes to you are adapted to your code, but the processing behind it is ultimately informed by code written by others.
|
||||
|
||||
How direct is the relationship between the suggested code and the code that informed it? In a recent thought-provoking paper<sup id="anchor1">[1](#footnote1)</sup>, Bender, Gebru et al. coined the phrase “stochastic parrots” for artificial intelligence systems like the ones that power {% data variables.product.prodname_dotcom %} Copilot. Or as a fellow machine learning engineer at {% data variables.product.company_short %}<sup id="anchor2">[2](#footnote2)</sup> remarked during a water cooler chat: these systems can feel like ”a toddler with a photographic memory.”
|
||||
|
||||
These are deliberate oversimplifications. Many {% data variables.product.prodname_dotcom %} Copilot suggestions feel pretty specifically tailored to the particular code base the user is working on. Often, it looks less like a parrot and more like a crow building novel tools out of small blocks<sup id="anchor3">[3](#footnote3)</sup>. But there’s no denying that {% data variables.product.prodname_dotcom %} Copilot has an impressive memory:
|
||||
|
||||
|
||||
|
||||
Here, I intentionally directed<sup id="anchor4">[4](#footnote4)</sup> {% data variables.product.prodname_dotcom %} Copilot to recite a well known text it obviously knows by heart. I, too, know a couple of texts by heart. For example, I still remember some poems I learnt in school. Yet no matter the topic, not once have I been tempted to derail a conversation by falling into iambic tetrameter and waxing about daffodils.
|
||||
|
||||
So is that (or rather the coding equivalent of it) something {% data variables.product.prodname_dotcom %} Copilot is prone to doing? How many of its suggestions are unique, and how often does it just parrot some likely looking code it has seen during training?
|
||||
|
||||
## The Experiment
|
||||
|
||||
During {% data variables.product.prodname_dotcom %} Copilot’s early development, nearly 300 employees used it in their daily work as part of an internal trial. This trial provided a good dataset to test for recitation. I wanted to find out how often {% data variables.product.prodname_dotcom %} Copilot gave them a suggestion that was quoted from something it had seen before.
|
||||
|
||||
I limited the investigation to Python suggestions with a cutoff on May 7, 2021 (the day we started extracting that data). That left 453,780 suggestions spread out over 396 “user weeks”, i.e. calendar weeks during which a user actively used {% data variables.product.prodname_dotcom %} Copilot on Python code.
|
||||
|
||||
### Automatic Filtering
|
||||
|
||||
453,780 suggestions are a lot, but many of them can be dismissed immediately. To get to the interesting cases, consider sequences of “words” that occur in the suggestion in the same order as in the code {% data variables.product.prodname_dotcom %} Copilot has been trained on. In this context, punctuation, brackets, or other special characters all count as “words”, while tabs, spaces or even line breaks are ignored completely. After all, a quote is still a quote, whether it’s indented by 1 tab or 8 spaces.
|
||||
|
||||
For example, one of {% data variables.product.prodname_dotcom %} Copilot’s suggestions was the following regex for numbers separated by whitespace:
|
||||
|
||||
```
|
||||
r'^\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+\s+\d+'
|
||||
```
|
||||
|
||||
This would be exactly 100 “words” in the sense above, but it’s a particularly dense example: the average non-empty line of code has only 10 “words.” I’ve restricted this investigation to cases where the overlap with the code {% data variables.product.prodname_dotcom %} Copilot was trained on contains at least 60 such “words”. We have to set the cut somewhere, and I think it’s rather rare that shorter sequences would be of great interest. In fact, most of the interesting cases identified later are well clear of that threshold of 60.
|
||||
|
||||
If the overlap extends to what the user has already written, that also counts for the length. After all, the user may have written that context with the help of {% data variables.product.prodname_dotcom %} Copilot as well!
|
||||
|
||||
In the following example, the user has started writing a very common snippet. {% data variables.product.prodname_dotcom %} Copilot completes it. Even though the completion itself is rather short, together with the already existing code it clears the threshold and is retained.
|
||||
|
||||
|
||||
|
||||
This procedure is permissive enough to let many relatively “boring” examples through, like the two above. But it’s still effective at dialing in the human analysis to the interesting cases, sorting out over 99% of Copilot suggestions.
|
||||
|
||||
### Manual Bucketing
|
||||
|
||||
After filtering, there were 473 suggestions left. But they came in very different forms:
|
||||
|
||||
1. Some were basically just repeats of another case that passed filtering. For example, sometimes {% data variables.product.prodname_dotcom %} Copilot makes a suggestion, the developer types a comment line, and {% data variables.product.prodname_dotcom %} Copilot offers a very similar suggestion again. I removed these cases from the analysis as duplicates.
|
||||
2. Some were long, repetitive sequences. Like the following example, where the repeated blocks of `‘<p>’` are of course found somewhere in the training set: <br><br> Such suggestions can be helpful (test cases, regular expressions) or not helpful (like this case, I suspect). But in any case, they do not fit the idea of rote learning I had in mind when I started this investigation.
|
||||
3. Some were standard inventories, like the natural numbers, or the prime numbers, or stock market tickers, or the Greek alphabet: <br>
|
||||
4. Some were common, straightforward ways, perhaps even universal ways, of doing things with very few natural degrees of freedom. For example, the middle part of the following strikes me as very much the standard way of using the BeautifulSoup package to parse a Wikipedia list. In fact, the best matching snippet found in {% data variables.product.prodname_dotcom %} Copilot's training data<sup id="anchor5">[5](#footnote5)</sup> uses such code to parse a different article and goes on to do different things with the results. <br> <br>This doesn’t fit my idea of a quote either. It’s a bit like when someone says “I’m taking out the trash; I’ll be back soon” -- that’s a matter of fact statement, not a quote, even though that particular phrase has been uttered many times before.
|
||||
5. And then there are all other cases. Those with at least some specific overlap in either code or comments. These are what interests me most, and what I’m going to concentrate on from now on.
|
||||
|
||||
This bucketing necessarily has some edge cases<sup id="anchor6">[6](#footnote6)</sup>, and your mileage may vary in how you think they should be classified. Maybe you even disagree with the whole set of buckets in the first place.
|
||||
|
||||
That’s why we’ve open sourced that dataset<sup id="anchor7">[7](#footnote7)</sup>. So if you feel a bit differently about the bucketing, or if you’re interested in other aspects of GitHub Copilot parroting its training set, you’re very welcome to just ignore my next section and draw your own conclusions.
|
||||
|
||||
## 結果
|
||||
|
||||
|
||||
|
||||
For most of {% data variables.product.prodname_dotcom %} Copilot's suggestions, our automatic filter didn’t find any significant overlap with the code used for training. But it did bring 473 cases to our attention. Removing the first bucket (cases that look very similar to other cases) left me with 185 suggestions. Of these, 144 got sorted out in buckets 2 - 4. This left 41 cases in the last bucket, the “recitations”, in the meaning of the term I have in mind.
|
||||
|
||||
That corresponds to **1 recitation event every 10 user weeks** (95% confidence interval: 7 - 13 weeks, using a Poisson test).
|
||||
|
||||
Of course, this was measured on the {% data variables.product.prodname_dotcom %} and Microsoft developers who tried out {% data variables.product.prodname_dotcom %} Copilot. If your coding behaviour is very different from theirs, your results might differ. In particular, some of these developers are only working part time on Python projects —— I could not distinguish that and so counted everyone who writes some Python in a given week as a user.
|
||||
|
||||
1 event in 10 weeks doesn’t sound like a lot, but it’s not 0 either. And I found three things that struck me.
|
||||
|
||||
### {% data variables.product.prodname_dotcom %} Copilot quotes when it lacks specific context
|
||||
|
||||
If I want to learn the lyrics to a song, I have to listen to it many times. {% data variables.product.prodname_dotcom %} Copilot is no different: to learn a snippet of code by heart, it must see that snippet a lot. Each file is only shown to {% data variables.product.prodname_dotcom %} Copilot once, so the snippet needs to exist in many different files in public code.
|
||||
|
||||
Of the 41 main cases we singled out during manual labelling, none appear in less than 10 different files. Most (35 cases) appear over a hundred times. Once, {% data variables.product.prodname_dotcom %} Copilot suggested starting an empty file with something it had even seen more than a whopping 700,000 different times during training -- that was the GNU General Public License.
|
||||
|
||||
The following plot shows the number of matched files of the results in bucket 5 (one red mark on the bottom for each result) versus buckets 2-4. I left out bucket 1, which is really just a mix of duplicates of bucket 2-4 cases and duplicates of bucket 5 cases. The inferred distribution is displayed as a red line; it peaks between 100 and 1000 matches.
|
||||
|
||||
|
||||
|
||||
### {% data variables.product.prodname_dotcom %} Copilot mostly quotes in generic contexts
|
||||
|
||||
As time goes on, each file becomes unique. But {% data variables.product.prodname_dotcom %} Copilot doesn’t wait for that<sup id="anchor8">[8](#footnote8)</sup>: it will offer its solutions while your file is still extremely generic. And in the absence of anything specific to go on, it’s much more likely to quote from somewhere else than it would be otherwise.
|
||||
|
||||
|
||||
|
||||
Of course, software developers spend most of their time deep inside the files, where the context is unique enough that {% data variables.product.prodname_dotcom %} Copilot will offer unique suggestions. In contrast, the suggestions at the beginning are rather hit-and-miss, since {% data variables.product.prodname_dotcom %} Copilot cannot know what the program will be. But sometimes, especially in toy projects or standalone scripts, a modest amount of context can be enough to hazard a reasonable guess of what the user wanted to do. And sometimes it's still generic enough so that {% data variables.product.prodname_dotcom %} Copilot thinks one of the solutions it knows by heart looks promising:
|
||||
|
||||
|
||||
|
||||
This is pretty much directly taken from coursework for a robotics class uploaded in different variations<sup id="anchor9">[9](#footnote9)</sup>.
|
||||
|
||||
### Detection is only as good as the tool that does the detecting
|
||||
|
||||
In its current form, the filter will turn up a good number of uninteresting cases when applied broadly. But it still should not be too much noise. For the internal users in the experiment, it would have been a bit more than one find per week on average (albeit likely in bursts!). Of these, about 17% (95% confidence interval using a binomial test: 14%-21%) would be in the fifth bucket.
|
||||
|
||||
And nothing is ever foolproof of course: so this too can be tricked. Some cases are rather hard to detect by the tool we’re building, but still have an obvious source. To return to the Zen of Python:
|
||||
|
||||
|
||||
|
||||
## Conclusion and Next Steps
|
||||
|
||||
This investigation demonstrates that {% data variables.product.prodname_dotcom %} Copilot _can_ quote a body of code verbatim, but that it rarely does so, and when it does, it mostly quotes code that everybody quotes, and mostly at the beginning of a file, as if to break the ice.
|
||||
|
||||
But there’s still one big difference between GitHub Copilot reciting code and me reciting a poem: I _know_ when I’m quoting. I would also like to know when Copilot is echoing existing code rather than coming up with its own ideas. That way, I’m able to look up background information about that code, and to include credit where credit is due.
|
||||
|
||||
The answer is obvious: sharing the prefiltering solution we used in this analysis to detect overlap with the training set. When a suggestion contains snippets copied from the training set, the UI should simply tell you where it’s quoted from. You can then either include proper attribution or decide against using that code altogether.
|
||||
|
||||
This duplication search is not yet integrated into the technical preview, but we plan to do so. And we will both continue to work on decreasing rates of recitation, and on making its detection more precise.
|
||||
|
||||
<br><br>
|
||||
|
||||
### Footnotes
|
||||
|
||||
<a name="footnote1">1</a>: [On the Dangers of Stochastic Parrots: Can Language Models Be Too Big?](https://dl.acm.org/doi/10.1145/3442188.3445922) [^](#anchor1)
|
||||
|
||||
<a name="footnote2">2</a>: [Tiferet Gazit](https://github.com/tiferet) [^](#anchor2)
|
||||
|
||||
<a name="footnote3">3</a>: see von Bayern et al. about the creative wisdom of crows: [Compound tool construction by New Caledonian crows](https://www.nature.com/articles/s41598-018-33458-z) [^](#anchor3)
|
||||
|
||||
<a name="footnote4">4</a>: see Carlini et al. about deliberately triggering the recall of training data: [Extracting Training Data from Large Language Models](https://arxiv.org/pdf/2012.07805.pdf) [^](#anchor4)
|
||||
|
||||
<a name="footnote5">5</a>: jaeteekae: [DelayedTwitter](https://github.com/jaeteekae/DelayedTwitter/blob/0a0b03de74c03cfbf36877ffded0cb1312d59642/get_top_twitter_accounts.py#L21) [^](#anchor5)
|
||||
|
||||
<a name="footnote6">6</a>: Probably not _too_ many though. I’ve asked some developers to help me label the cases, and everyone was prompted to flag up any uncertainty with their judgement. That happened in only 34 cases, i.e. less than 10%. [^](#anchor6)
|
||||
|
||||
<a name="footnote7">7</a>: In the [public dataset](/assets/images/help/copilot/matched_snippets.csv), I list the part of Copilot's suggestion that was also found in the training set, how often it was found, and a link to an example where it occurs in public code. For privacy reasons, I don't include the not-matched part of the completion or the code context the user had typed (only an indication of its length). [^](#anchor7)
|
||||
|
||||
<a name="footnote8">8</a>: In fact, since this experiment has been made, {% data variables.product.prodname_dotcom %} Copilot _has_ changed to require a minimum file content. So some of the suggestions flagged here would not have been shown by the current version. [^](#anchor8)
|
||||
|
||||
<a name="footnote9">9</a>: For example jenevans33: [CS8803-1](https://github.com/jenevans33/CS8803-1/blob/eca1bbc27ca6f7355dbc806b2f95964b59381605/src/Final/ekfcode.py#L23) [^](#anchor9)
|
||||
@@ -322,6 +322,8 @@ sections:
|
||||
Focusing or hovering over a label now displays the label description in a tooltip.
|
||||
- |
|
||||
Creating and removing repository invitations, whether done through the API or web interface, are now subject to rate limits that may be enabled on your GitHub Enterprise Server instance. For more information about rate limits, see "[Configuring rate limits](/admin/configuration/configuring-your-enterprise/configuring-rate-limits)."
|
||||
- |
|
||||
MinIO has announced the removal of the MinIO Gateways starting June 1st, 2022. While MinIO Gateway for NAS continues to be one of the supported storage providers for Github Actions and Github Packages, we recommend moving to MinIO LTS support to avail support and bug fixes from MinIO. For more information about rate limits, see "[Scheduled removal of MinIO Gateway for GCS, Azure, HDFS in the minio/minio repository](https://github.com/minio/minio/issues/14331)."
|
||||
deprecations:
|
||||
-
|
||||
heading: Change to the format of authentication tokens
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
{% ifversion ghec %}
|
||||
If your license includes {% data variables.product.prodname_vss_ghe %}, you can identify whether a personal account on {% data variables.product.prodname_dotcom_the_website %} has successfully matched with a {% data variables.product.prodname_vs %} subscriber by downloading the CSV file that contains additional license details. The license status will be one of the following.
|
||||
- "Matched": The personal account on {% data variables.product.prodname_dotcom_the_website %} is linked with a {% data variables.product.prodname_vs %} subscriber.
|
||||
If your license includes {% data variables.product.prodname_vss_ghe %}, you can identify whether a user account on {% data variables.product.prodname_dotcom_the_website %} has successfully matched with a {% data variables.product.prodname_vs %} subscriber by downloading the CSV file that contains additional license details. The license status will be one of the following.
|
||||
- "Matched": The user account on {% data variables.product.prodname_dotcom_the_website %} is linked with a {% data variables.product.prodname_vs %} subscriber.
|
||||
- "Pending Invitation": An invitation was sent to a {% data variables.product.prodname_vs %} subscriber, but the subscriber has not accepted the invitation.
|
||||
- Blank: There is no {% data variables.product.prodname_vs %} association to consider for the personal account on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
- Blank: There is no {% data variables.product.prodname_vs %} association to consider for the user account on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
{% endif %}
|
||||
|
||||
@@ -1,30 +0,0 @@
|
||||
With per-user pricing, each person consumes one license. {% data variables.product.company_short %} identifies individuals by primary email address.
|
||||
|
||||
{% data variables.product.company_short %} bills for the following people.
|
||||
|
||||
{%- ifversion ghec %}
|
||||
- Enterprise owners who are a member or owner of at least one organization in the enterprise
|
||||
{%- endif %}
|
||||
- Organization members, including owners
|
||||
- Outside collaborators on private{% ifversion ghec %} or internal{% endif %} repositories owned by your organization, excluding forks
|
||||
- Anyone with a pending invitation to become an organization owner or member
|
||||
- Anyone with a pending invitation to become an outside collaborator on private{% ifversion ghec %} or internal{% endif %} repositories owned by your organization, excluding forks
|
||||
{%- ifversion ghec %}
|
||||
- Each user on any {% data variables.product.prodname_ghe_server %} instance that you deploy
|
||||
{% endif %}
|
||||
|
||||
{% data variables.product.company_short %} does not bill for any of the following people.
|
||||
|
||||
{%- ifversion ghec %}
|
||||
- Enterprise owners who are not a member or owner of at least one organization in the enterprise
|
||||
- Enterprise billing managers
|
||||
{%- endif %}
|
||||
- Organization billing managers{% ifversion ghec %} for individual organizations on {% data variables.product.prodname_ghe_cloud %}{% endif %}
|
||||
- Anyone with a pending invitation to become an{% ifversion ghec %} enterprise or{% endif %} organization billing manager
|
||||
- Anyone with a pending invitation to become an outside collaborator on a public repository owned by your organization
|
||||
|
||||
{% note %}
|
||||
|
||||
**注釈**: {% data reusables.organizations.org-invite-scim %}
|
||||
|
||||
{% endnote %}
|
||||
@@ -0,0 +1,25 @@
|
||||
| オプション | 必須 | Security Updates | Version Updates | 説明 |
|
||||
|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |:-----:|:----------------:|:---------------:|:----------------------------------------------------------------------- |
|
||||
| [`package-ecosystem`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#package-ecosystem) | **X** | | X | 使用するパッケージマネージャー |
|
||||
| [`directory`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#directory) | **X** | | X | パッケージマニフェストの場所 |
|
||||
| [`schedule.interval`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduleinterval) | **X** | | X | 更新を確認する頻度 |
|
||||
| [`allow`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#allow) | | X | X | 許可する更新をカスタマイズする |
|
||||
| [`assignees`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#assignees) | | X | X | プルリクエストのアサイン担当者 |
|
||||
| [`commit-message`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#commit-message) | | X | X | コミットメッセージの設定 |{% ifversion fpt or ghec or ghes > 3.4 %}
|
||||
| [`enable-beta-ecosystems`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#enable-beta-ecosystems) | | | X | ベータレベルのサポートがあるエコシステムを有効にする
|
||||
{% endif %}
|
||||
| [`ignore`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#ignore) | | X | X | 特定の依存関係またはバージョンを無視する |
|
||||
| [`insecure-external-code-execution`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#insecure-external-code-execution) | | | X | マニフェストファイル内でコードの実行を許可または拒否する |
|
||||
| [`labels`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#labels) | | X | X | プルリクエストに設定するラベル |
|
||||
| [`マイルストーン`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#milestone) | | X | X | プルリクエストに設定するマイルストーン |
|
||||
| [`open-pull-requests-limit`](#open-pull-requests-limit) | | X | X | バージョン更新時のオープンなプルリクエスト数を制限する |
|
||||
| [`pull-request-branch-name.separator`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#pull-request-branch-nameseparator) | | X | X | プルリクエストブランチ名の区切り文字を変更する |
|
||||
| [`rebase-strategy`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#rebase-strategy) | | X | X | 自動リベースを無効にする |
|
||||
| [`registries`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#registries) | | | X | {% data variables.product.prodname_dependabot %} がアクセスできるプライベートリポジトリ |
|
||||
| [`レビュー担当者`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#reviewers) | | X | X | プルリクエストのレビュー担当者 |
|
||||
| [`schedule.day`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduleday) | | | X | 更新を確認する曜日 |
|
||||
| [`schedule.time`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduletime) | | | X | 更新を確認する時刻 (hh:mm) |
|
||||
| [`schedule.timezone`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#scheduletimezone) | | | X | 時刻のタイムゾーン（ゾーン識別子） |
|
||||
| [`target-branch`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#target-branch) | | X | X | プルリクエストを作成するブランチ |
|
||||
| [`vendor`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#vendor) | | | X | ベンダーまたはキャッシュされた依存関係を更新する |
|
||||
| [`versioning-strategy`](/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#versioning-strategy) | | X | X | マニフェストのバージョン要件の更新方法 |
|
||||
@@ -1,5 +1,3 @@
|
||||
{% data variables.product.prodname_enterprise %} uses a unique-user licensing model, where each person only consumes one license, no matter how many {% data variables.product.prodname_ghe_server %} instances the person uses, or how many organizations the person is a member of on {% data variables.product.prodname_ghe_cloud %}. This model allows each person to use multiple {% data variables.product.prodname_enterprise %} environments without incurring extra costs.
|
||||
For a person using multiple {% data variables.product.prodname_enterprise %} environments to only consume a single license, you must synchronize license usage between environments. Then, {% data variables.product.company_short %} will deduplicate users based on the email addresses associated with their user accounts. Multiple user accounts will consume a single license when there is a match between an account's primary email address on {% data variables.product.prodname_ghe_server %} and/or an account's verified email address on {% data variables.product.prodname_dotcom_the_website %}. For more information about verification of email addresses on {% data variables.product.prodname_dotcom_the_website %}, see "[Verifying your email address](/enterprise-cloud@latest/get-started/signing-up-for-github/verifying-your-email-address){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
|
||||
For a person using multiple {% data variables.product.prodname_enterprise %} environments to only consume a single license, you must synchronize license usage between environments. Then, {% data variables.product.company_short %} will deduplicate users based on the email addresses associated with their personal accounts. Multiple personal accounts will consume a single license when there is a match between an account's primary email address on {% data variables.product.prodname_ghe_server %} and/or an account's verified email address on {% data variables.product.prodname_dotcom_the_website %}. For more information about verification of email addresses on {% data variables.product.prodname_dotcom_the_website %}, see "[Verifying your email address](/enterprise-cloud@latest/get-started/signing-up-for-github/verifying-your-email-address){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
|
||||
When you synchronize license usage, only the user ID and email addresses for each personal account on {% data variables.product.prodname_ghe_server %} are transmitted to {% data variables.product.prodname_ghe_cloud %}.
|
||||
When you synchronize license usage, only the user ID and email addresses for each user account on {% data variables.product.prodname_ghe_server %} are transmitted to {% data variables.product.prodname_ghe_cloud %}.
|
||||
@@ -0,0 +1,3 @@
|
||||
{% data variables.product.company_short %} uses a unique-user licensing model. For enterprise products that include multiple deployment options, {% data variables.product.company_short %} determines how many licensed seats you're consuming based on the number of unique users across all your deployments.
|
||||
|
||||
Each user account only consumes one license, no matter how many {% data variables.product.prodname_ghe_server %} instances the user account uses, or how many organizations the user account is a member of on {% data variables.product.prodname_ghe_cloud %}. This model allows each person to use multiple {% data variables.product.prodname_enterprise %} deployments without incurring extra costs.
|
||||
@@ -1,5 +1,5 @@
|
||||
{% note %}
|
||||
|
||||
**Note:** If you synchronize license usage and your enterprise account on {% data variables.product.prodname_dotcom_the_website %} does not use {% data variables.product.prodname_emus %}, we highly recommend enabling verified domains for your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. For privacy reasons, your consumed license report only includes the email address associated with a personal account on {% data variables.product.prodname_dotcom_the_website %} if the address is hosted by a verified domain. If one person is erroneously consuming multiple licenses, having access to the email address that is being used for deduplication makes troubleshooting much easier. For more information. see "[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" and "[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
**Note:** If you synchronize license usage and your enterprise account on {% data variables.product.prodname_dotcom_the_website %} does not use {% data variables.product.prodname_emus %}, we highly recommend enabling verified domains for your enterprise account on {% data variables.product.prodname_dotcom_the_website %}. For privacy reasons, your consumed license report only includes the email address associated with a user account on {% data variables.product.prodname_dotcom_the_website %} if the address is hosted by a verified domain. If one person is erroneously consuming multiple licenses, having access to the email address that is being used for deduplication makes troubleshooting much easier. For more information, see {% ifversion ghec or ghes > 3.1 %}"[Verifying or approving a domain for your enterprise](/enterprise-cloud@latest/admin/configuration/configuring-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise)" and {% endif %}"[About {% data variables.product.prodname_emus %}](/enterprise-cloud@latest/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/about-enterprise-managed-users){% ifversion not ghec %}" in the {% data variables.product.prodname_ghe_cloud %} documentation.{% else %}."{% endif %}
|
||||
|
||||
{% endnote %}
|
||||
@@ -1,4 +1,4 @@
|
||||
When using the **Rebase and Merge** option on a pull request, it's important to note that the commits in the head branch are added to the base branch without commit signature verification. When you use this option, {% data variables.product.prodname_dotcom %} creates a modified commit, using the data and content of the original commit. This means that{% data variables.product.prodname_dotcom %} didn't truly create this commit, and can't therefore sign it as a generic system user.
|
||||
When using the **Rebase and Merge** option on a pull request, it's important to note that the commits in the head branch are added to the base branch without commit signature verification. When you use this option, {% data variables.product.prodname_dotcom %} creates a modified commit, using the data and content of the original commit. This means that {% data variables.product.prodname_dotcom %} didn't truly create this commit, and can't therefore sign it as a generic system user.
|
||||
{% data variables.product.prodname_dotcom %} doesn't have access to the committer's private signing keys, so it can't sign the commit on the user's behalf.
|
||||
|
||||
A workaround for this is to rebase and merge locally, and then push the changes to the pull request's base branch.
|
||||
|
||||
@@ -142,6 +142,7 @@ prodname_codeql_workflow: 'CodeQL分析ワークフロー'
|
||||
prodname_vs: 'Visual Studio'
|
||||
prodname_vscode_shortname: 'VS Code'
|
||||
prodname_vscode: 'Visual Studio Code'
|
||||
prodname_vs_subscriber: '{% data variables.product.prodname_vs %} subscriber'
|
||||
prodname_vss_ghe: 'Visual Studio subscriptions with GitHub Enterprise'
|
||||
prodname_vss_admin_portal_with_url: '[Visual Studio subscriptions管理ポータル](https://visualstudio.microsoft.com/subscriptions-administration/)'
|
||||
prodname_vscode_command_palette_shortname: 'VS Code Command Palette'
|
||||
|
||||
@@ -80,7 +80,6 @@ translations/ja-JP/content/billing/managing-billing-for-github-advanced-security
|
||||
translations/ja-JP/content/billing/managing-billing-for-github-advanced-security/viewing-your-github-advanced-security-usage.md,rendering error
|
||||
translations/ja-JP/content/billing/managing-billing-for-github-packages/about-billing-for-github-packages.md,broken liquid tags
|
||||
translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-billing-for-your-enterprise.md,broken liquid tags
|
||||
translations/ja-JP/content/billing/managing-billing-for-your-github-account/about-per-user-pricing.md,broken liquid tags
|
||||
translations/ja-JP/content/billing/managing-billing-for-your-github-account/how-does-upgrading-or-downgrading-affect-the-billing-process.md,broken liquid tags
|
||||
translations/ja-JP/content/billing/managing-billing-for-your-github-account/viewing-the-subscription-and-usage-for-your-enterprise-account.md,broken liquid tags
|
||||
translations/ja-JP/content/billing/managing-licenses-for-visual-studio-subscriptions-with-github-enterprise/about-visual-studio-subscriptions-with-github-enterprise.md,broken liquid tags
|
||||
@@ -272,9 +271,9 @@ translations/ja-JP/data/reusables/dotcom_billing/lfs-remove-data.md,broken liqui
|
||||
translations/ja-JP/data/reusables/education/apply-for-team.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/actions-tab.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md,Listed in localization-support#489
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md,rendering error
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/hooks-tab.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md,Listed in localization-support#489
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md,rendering error
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/messages-tab.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/enterprise-accounts/pages-tab.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/enterprise_installation/hardware-considerations-all-platforms.md,broken liquid tags
|
||||
translations/ja-JP/data/reusables/enterprise_installation/upgrade-hardware-requirements.md,broken liquid tags
|
||||
|
||||
|
Reference in New Issue
Block a user