зеркало из https://github.com/github/docs.git
Merge branch 'main' into release-contributor-facepiles-updated
This commit is contained in:
Sarita Iyer
GitHub
Коммит
243bf2b0ea
|
|
@ -85,9 +85,8 @@ async function run() {
|
|||
),
|
||||
'utf8'
|
||||
)
|
||||
const issueLabels = milestone === 'release'
|
||||
? ['enterprise release']
|
||||
: ['enteprise deprecation', 'priority-3']
|
||||
const issueLabels =
|
||||
milestone === 'release' ? ['enterprise release'] : ['enterprise deprecation', 'priority-3']
|
||||
const issueTitle = `[${nextMilestoneDate}] Enterprise Server ${versionNumber} ${milestone} (technical steps)`
|
||||
|
||||
const issueBody = `GHES ${versionNumber} ${milestone} occurs on ${nextMilestoneDate}.
|
||||
|
|
|
|||
|
|
@ -106,5 +106,8 @@ This file should be automatically updated, but you can also run `script/update-e
|
|||
- [ ] Remove `[DO NOT MERGE]` and other meta information from the PR title 😜.
|
||||
- [ ] The `github/docs-internal` repo is frozen, and the `Repo Freeze Check / Prevent merging during deployment freezes (pull_request_target)` test is expected to fail. Use admin permissions to ship the release branch with this failure.
|
||||
- [ ] Do any required smoke tests.
|
||||
- [ ] Push the search index LFS objects for the public `github/docs` repo. The LFS objects were already being pushed for the internal repo after the `sync-english-index-for-<PLAN@RELEASE>` was added to the megabranch. To push the LFS objects, run the [search sync workflow](https://github.com/github/docs-internal/actions/workflows/sync-search-indices.yml) with the following inputs:
|
||||
version: `enterprise-server@<RELEASE>`
|
||||
language: `en`
|
||||
- [ ] Once smoke tests have passed, you can [unfreeze the repos](https://github.com/github/docs-content/blob/main/docs-content-docs/docs-content-workflows/freezing.md) and post an announcement in Slack.
|
||||
- [ ] After the release, in the `docs-content` repo, add the now live version number to the "Specific GHES version(s)" section in the following files: [`.github/ISSUE_TEMPLATE/release-tier-1-or-2-tracking.yml`](https://github.com/github/docs-content/blob/main/.github/ISSUE_TEMPLATE/release-tier-1-or-2-tracking.yml) and [`.github/ISSUE_TEMPLATE/release-tier-3-or-tier-4.yml`](https://github.com/github/docs-content/blob/main/.github/ISSUE_TEMPLATE/release-tier-3-or-tier-4.yml). When the PR is approved, merge it in.
|
||||
|
|
@ -9,9 +9,13 @@ on:
|
|||
schedule:
|
||||
- cron: '50 */6 * * *'
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
add-requests-to-board:
|
||||
name: Add requests to board
|
||||
if: ${{ github.repository == 'github/docs-internal' }}
|
||||
runs-on: ubuntu-latest
|
||||
|
||||
steps:
|
||||
|
|
@ -31,7 +35,7 @@ jobs:
|
|||
run: |
|
||||
node .github/actions-scripts/fr-add-docs-reviewers-requests.js
|
||||
env:
|
||||
TOKEN: ${{ secrets.DOCS_BOT }}
|
||||
TOKEN: ${{ secrets.DOCS_BOT_FR }}
|
||||
PROJECT_NUMBER: 2936
|
||||
ORGANIZATION: 'github'
|
||||
REPO: 'github'
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ jobs:
|
|||
run: |
|
||||
script/update-enterprise-dates.js
|
||||
env:
|
||||
GITHUB_TOKEN: ${{ secrets.DOCS_BOT }}
|
||||
GITHUB_TOKEN: ${{ secrets.DOCS_BOT_FR }}
|
||||
|
||||
- name: Create pull request
|
||||
id: create-pull-request
|
||||
|
|
|
|||
|
|
@ -32,25 +32,25 @@ jobs:
|
|||
run: |
|
||||
.github/actions-scripts/check-for-enterprise-issues-by-label.js
|
||||
env:
|
||||
GITHUB_TOKEN: ${{ secrets.DOCS_BOT }}
|
||||
GITHUB_TOKEN: ${{ secrets.DOCS_BOT_FR }}
|
||||
|
||||
- name: Update enterprise dates
|
||||
if: steps.existingIssue.outputs.deprecationIssue == 'false' || steps.existingIssue.outputs.releaseIssue == 'false'
|
||||
run: |
|
||||
script/update-enterprise-dates.js
|
||||
env:
|
||||
GITHUB_TOKEN: ${{ secrets.DOCS_BOT }}
|
||||
GITHUB_TOKEN: ${{ secrets.DOCS_BOT_FR }}
|
||||
|
||||
- name: Create an enterprise release issue
|
||||
if: steps.existingIssue.outputs.releaseIssue == 'false'
|
||||
run: |
|
||||
.github/actions-scripts/create-enterprise-issue.js release
|
||||
env:
|
||||
GITHUB_TOKEN: ${{ secrets.DOCS_BOT }}
|
||||
GITHUB_TOKEN: ${{ secrets.DOCS_BOT_FR }}
|
||||
|
||||
- name: Create an enterprise deprecation issue
|
||||
if: steps.existingIssue.outputs.deprecationIssue == 'false'
|
||||
run: |
|
||||
.github/actions-scripts/create-enterprise-issue.js deprecation
|
||||
env:
|
||||
GITHUB_TOKEN: ${{ secrets.DOCS_BOT }}
|
||||
GITHUB_TOKEN: ${{ secrets.DOCS_BOT_FR }}
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ jobs:
|
|||
run: |
|
||||
node .github/actions-scripts/ready-for-docs-review.js
|
||||
env:
|
||||
TOKEN: ${{ secrets.DOCS_BOT }}
|
||||
TOKEN: ${{ secrets.DOCS_BOT_FR }}
|
||||
PROJECT_NUMBER: 2936
|
||||
ORGANIZATION: 'github'
|
||||
PR_NODE_ID: ${{ github.event.pull_request.node_id }}
|
||||
|
|
|
|||
|
|
@ -15,7 +15,6 @@ on:
|
|||
|
||||
permissions:
|
||||
contents: read
|
||||
deployments: write
|
||||
pull-requests: read
|
||||
|
||||
jobs:
|
||||
|
|
@ -40,7 +39,7 @@ jobs:
|
|||
run: script/remove-stale-staging-apps.js
|
||||
env:
|
||||
HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }}
|
||||
GITHUB_TOKEN: ${{ secrets.DOCUBOT_FR_PROJECT_BOARD_WORKFLOWS_REPO_ORG_READ_SCOPES }}
|
||||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||
|
||||
remove_stale_staging_envs:
|
||||
name: Remove stale staging environments
|
||||
|
|
@ -61,5 +60,5 @@ jobs:
|
|||
- name: Run script
|
||||
run: script/remove-stale-staging-envs.js
|
||||
env:
|
||||
GITHUB_TOKEN: ${{ secrets.DOCUBOT_FR_PROJECT_BOARD_WORKFLOWS_REPO_ORG_READ_SCOPES }}
|
||||
GITHUB_TOKEN: ${{ secrets.DOCS_BOT_FR }}
|
||||
REPO: ${{ github.repository }}
|
||||
|
|
|
|||
|
|
@ -126,6 +126,8 @@ jobs:
|
|||
env:
|
||||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||
HEROKU_API_TOKEN: ${{ secrets.HEROKU_API_TOKEN }}
|
||||
HYDRO_ENDPOINT: ${{ secrets.HYDRO_ENDPOINT }}
|
||||
HYDRO_SECRET: ${{ secrets.HYDRO_SECRET }
|
||||
with:
|
||||
script: |
|
||||
const esm = require('esm')
|
||||
|
|
|
|||
|
|
@ -21,6 +21,15 @@ name: Sync search indexes
|
|||
|
||||
on:
|
||||
workflow_dispatch:
|
||||
inputs:
|
||||
language:
|
||||
description: 'Language to generate the search index for. Can be one of: `en` English, `cn` Chinese simplified, `ja` Japanese, `es` Spanish, `pt` Portuguese., `all` all languages.'
|
||||
required: false
|
||||
default: 'all'
|
||||
version:
|
||||
description: 'Version to generate the search index for. Can be one of: `free-pro-team@latest`, `enterprise-server@<RELEASE NUMBER>`, `github-ae@latest`, `all` all versions.'
|
||||
required: false
|
||||
default: 'all'
|
||||
schedule:
|
||||
- cron: '53 0/8 * * *' # Run every eight hours at 53 minutes past the hour
|
||||
|
||||
|
|
@ -41,7 +50,7 @@ jobs:
|
|||
- name: checkout
|
||||
uses: actions/checkout@5a4ac9002d0be2fb38bd78e4b4dbde5606d7042f
|
||||
with:
|
||||
token: ${{ secrets.DOCS_BOT }}
|
||||
token: ${{ secrets.DOCS_BOT_FR }}
|
||||
|
||||
- name: Setup Node
|
||||
uses: actions/setup-node@38d90ce44d5275ad62cc48384b3d8a58c500bb5f
|
||||
|
|
@ -58,6 +67,8 @@ jobs:
|
|||
- name: Update search indexes
|
||||
env:
|
||||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||
VERSION: ${{ github.event.inputs.version }}
|
||||
LANGUAGE: ${{ github.event.inputs.language }}
|
||||
run: npm run sync-search
|
||||
|
||||
- name: Update private docs repository search indexes
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ jobs:
|
|||
- name: Run updater scripts
|
||||
env:
|
||||
# need to use a token from a user with access to github/github for this step
|
||||
GITHUB_TOKEN: ${{ secrets.DOCS_BOT }}
|
||||
GITHUB_TOKEN: ${{ secrets.DOCS_BOT_FR }}
|
||||
run: |
|
||||
script/graphql/update-files.js
|
||||
- name: Create pull request
|
||||
|
|
|
|||
Двоичный файл не отображается.
|
После Ширина: | Высота: | Размер: 965 KiB |
Двоичный файл не отображается.
|
После Ширина: | Высота: | Размер: 62 KiB |
Двоичные данные
assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png
Normal file
Двоичные данные
assets/images/help/repository/secret-scanning-confirm-deletion-custom-pattern.png
Normal file
Двоичный файл не отображается.
|
После Ширина: | Высота: | Размер: 82 KiB |
Двоичный файл не отображается.
|
До Ширина: | Высота: | Размер: 58 KiB После Ширина: | Высота: | Размер: 162 KiB |
Двоичный файл не отображается.
|
До Ширина: | Высота: | Размер: 23 KiB |
|
|
@ -14,7 +14,7 @@ topics:
|
|||
- Profiles
|
||||
shortTitle: Organization's profile
|
||||
---
|
||||
You can optionally choose to add a description, location, website, and email address for your organization, and pin important repositories to the top of the page.
|
||||
You can optionally choose to add a description, location, website, and email address for your organization, and pin important repositories. You can customize your organization's profile by adding a README.md file. For more information, see "[Customizing your organization's profile](/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile)."
|
||||
|
||||
{% ifversion fpt %}To confirm your organization's identity and display a "Verified" badge on your organization profile page, you must verify your organization's domains with {% data variables.product.product_name %}. For more information, see "[Verifying or approving a domain for your organization](/organizations/managing-organization-settings/verifying-or-approving-a-domain-for-your-organization)."{% endif %}
|
||||
|
||||
|
|
|
|||
|
|
@ -118,6 +118,6 @@ jobs:
|
|||
|
||||
The following resources may also be useful:
|
||||
|
||||
* For the original starter workflow, see [`azure.yml`](https://github.com/actions/starter-workflows/blob/master/ci/azure.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
|
||||
* For the original starter workflow, see [`azure.yml`](https://github.com/actions/starter-workflows/blob/main/deployments/azure.yml) in the {% data variables.product.prodname_actions %} `starter-workflows` repository.
|
||||
* The action used to deploy the web app is the official Azure [`Azure/webapps-deploy`](https://github.com/Azure/webapps-deploy) action.
|
||||
* The "[Create a Node.js web app in Azure](https://docs.microsoft.com/en-us/azure/app-service/quickstart-nodejs)" quickstart in the Azure web app documentation demonstrates using VS Code with the [Azure App Service extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-azureappservice).
|
||||
|
|
|
|||
|
|
@ -180,7 +180,7 @@ jobs:
|
|||
|
||||
For more information on the tools used in these examples, see the following documentation:
|
||||
|
||||
* For the full starter workflow, see the ["Build and Deploy to GKE" workflow](https://github.com/actions/starter-workflows/blob/master/ci/google.yml).
|
||||
* For the full starter workflow, see the ["Build and Deploy to GKE" workflow](https://github.com/actions/starter-workflows/blob/main/deployments/google.yml).
|
||||
* For more starter workflows and accompanying code, see Google's [{% data variables.product.prodname_actions %} example workflows](https://github.com/google-github-actions/setup-gcloud/tree/master/example-workflows/).
|
||||
* The Kubernetes YAML customization engine: [Kustomize](https://kustomize.io/).
|
||||
* "[Deploying a containerized web application](https://cloud.google.com/kubernetes-engine/docs/tutorials/hello-app)" in the Google Kubernetes Engine documentation.
|
||||
|
|
|
|||
|
|
@ -42,11 +42,7 @@ For more information, see "[Core concepts for {% data variables.product.prodname
|
|||
|
||||
Jenkins lets you send builds to a single build agent, or you can distribute them across multiple agents. You can also classify these agents according to various attributes, such as operating system types.
|
||||
|
||||
Similarly, {% data variables.product.prodname_actions %} can send jobs to {% data variables.product.prodname_dotcom %}-hosted or self-hosted runners, and you can use labels to classify runners according to various attributes. The following table compares how the distributed build concept is implemented for both Jenkins and {% data variables.product.prodname_actions %}.
|
||||
|
||||
| Jenkins | {% data variables.product.prodname_actions %} |
|
||||
| ------------- | ------------- |
|
||||
| [`agents`](https://wiki.jenkins.io/display/JENKINS/Distributed+builds) | [`runners`](/actions/learn-github-actions/introduction-to-github-actions#runners) <br> [`self-hosted runners`](/actions/hosting-your-own-runners/about-self-hosted-runners) |
|
||||
Similarly, {% data variables.product.prodname_actions %} can send jobs to {% data variables.product.prodname_dotcom %}-hosted or self-hosted runners, and you can use labels to classify runners according to various attributes. For more information, see "[Understanding {% data variables.product.prodname_actions %}](/actions/learn-github-actions/understanding-github-actions#runners)" and "[About self-hosted runners](/actions/hosting-your-own-runners/about-self-hosted-runners)."
|
||||
|
||||
### Using sections to organize pipelines
|
||||
|
||||
|
|
|
|||
|
|
@ -79,4 +79,6 @@ You can also use the `ghe-ssl-acme` command line utility on {% data variables.pr
|
|||
{% data reusables.enterprise_management_console.privacy %}
|
||||
7. Click **Request TLS certificate**.
|
||||
|
||||
8. Click **Save configuration**.
|
||||
8. Wait for the "Status" to change from "STARTED" to "DONE".
|
||||
|
||||
9. Click **Save configuration**.
|
||||
|
|
|
|||
|
|
@ -79,5 +79,7 @@ Run the `ghe-upgrade` command, providing the package file name you downloaded in
|
|||
> gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
|
||||
> gpg: Good signature from "GitHub Enterprise (Upgrade Package Key) > <enterprise@github.com>"
|
||||
```
|
||||
5. The upgrade process will reboot the primary MySQL node once it completes. Verify that you can `ping` each node after it reboots.
|
||||
6. Exit maintenance mode from the administrative shell of any node by running `ghe-cluster-maintenance -u`.
|
||||
5. The upgrade process will reboot the primary MySQL node once it completes. Verify that you can `ping` each node after it reboots.{% ifversion ghes > 2.22 %}
|
||||
6. Connect to the administrative shell of the primary MySQL node and run the `ghe-cluster-config-apply` command.
|
||||
7. When `ghe-cluster-config-apply` is complete, check that the services are in a healthy state by running `ghe-cluster-status`.{% endif %}
|
||||
8. Exit maintenance mode from the administrative shell of any node by running `ghe-cluster-maintenance -u`.
|
||||
|
|
|
|||
|
|
@ -43,6 +43,8 @@ If you purchased {% data variables.product.prodname_enterprise %} through a Micr
|
|||
|
||||
For information on managing and changing your account's spending limit, see "[Managing your spending limit for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)."
|
||||
|
||||
{% data reusables.codespaces.exporting-changes %}
|
||||
|
||||
## How billing is handled for forked repositories
|
||||
|
||||
{% data variables.product.prodname_codespaces %} can only be used in organizations where a billable owner has been defined. To incur charges to the organization, the user must be a member or collaborator, otherwise they cannot create a codespace.
|
||||
|
|
|
|||
|
|
@ -46,5 +46,8 @@ Enterprise owners and billing managers can manage the spending limit for {% data
|
|||
{% data reusables.dotcom_billing.monthly-spending-limit %}
|
||||
{% data reusables.dotcom_billing.update-spending-limit %}
|
||||
|
||||
## Exporting changes when you have reached your spending limit
|
||||
|
||||
{% data reusables.codespaces.exporting-changes %}
|
||||
## Managing usage and spending limit email notifications
|
||||
{% data reusables.billing.email-notifications %}
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ topics:
|
|||
|
||||
{% data variables.product.company_short %} performs {% data variables.product.prodname_secret_scanning %} on {% ifversion fpt %}public and private{% endif %} repositories for secret patterns provided by {% data variables.product.company_short %} and {% data variables.product.company_short %} partners. For more information on the {% data variables.product.prodname_secret_scanning %} partner program, see "<a href="/developers/overview/secret-scanning-partner-program" class="dotcom-only">Secret scanning partner program</a>."
|
||||
|
||||
However, there can be situations where you want to scan for other secret patterns in your {% ifversion fpt %}private{% endif %} repositories. For example, you might have a secret pattern that is internal to your organization. For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in organizations and {% ifversion fpt %}private{% endif %} repositories on {% data variables.product.product_name %}. You can define up to 20 custom patterns for each {% ifversion fpt %}private{% endif %} repository or organization.
|
||||
However, there can be situations where you want to scan for other secret patterns in your {% ifversion fpt %}private{% endif %} repositories. For example, you might have a secret pattern that is internal to your organization. For these situations, you can define custom {% data variables.product.prodname_secret_scanning %} patterns in your enterprise, organization, or {% ifversion fpt %}private{% endif %} repository on {% data variables.product.product_name %}. You can define up to 20 custom patterns for each {% ifversion fpt %}private{% endif %} repository, organization, or enterprise account.
|
||||
|
||||
{% note %}
|
||||
|
||||
|
|
@ -47,7 +47,8 @@ Before defining a custom pattern, you must ensure that {% data variables.product
|
|||
{% data reusables.repositories.sidebar-settings %}
|
||||
{% data reusables.repositories.navigate-to-security-and-analysis %}
|
||||
{% data reusables.repositories.navigate-to-ghas-settings %}
|
||||
{% data reusables.repositories.secret-scanning-add-custom-pattern %}
|
||||
{% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
|
||||
{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
|
||||
|
||||
After your pattern is created, {% data reusables.secret-scanning.secret-scanning-process %} For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
|
||||
|
||||
|
|
@ -65,17 +66,43 @@ Before defining a custom pattern, you must ensure that you enable {% data variab
|
|||
{% data reusables.profile.org_settings %}
|
||||
{% data reusables.organizations.security-and-analysis %}
|
||||
{% data reusables.repositories.navigate-to-ghas-settings %}
|
||||
{% data reusables.repositories.secret-scanning-add-custom-pattern %}
|
||||
{% data reusables.advanced-security.secret-scanning-new-custom-pattern %}
|
||||
{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
|
||||
|
||||
After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt %}private{% endif %} repositories in your organization, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
|
||||
|
||||
## Defining a custom pattern for an enterprise account
|
||||
|
||||
Before defining a custom pattern, you must ensure that you enable secret scanning for your enterprise account. For more information, see "[Enabling {% data variables.product.prodname_GH_advanced_security %} for your enterprise](/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise)."
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** There is no dry-run functionality during the custom patterns beta. To avoid excess false-positive {% data variables.product.prodname_secret_scanning %} alerts, we recommend that you test your custom patterns in a repository before defining them for your entire enterprise.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.policies-tab %}
|
||||
{% data reusables.enterprise-accounts.advanced-security-policies %}
|
||||
{% data reusables.enterprise-accounts.advanced-security-security-features %}
|
||||
1. Under "Secret scanning custom patterns", click {% ifversion fpt or ghes > 3.2 or ghae-next %}**New pattern**{% elsif ghes = 3.2 %}**New custom pattern**{% endif %}.
|
||||
{% data reusables.advanced-security.secret-scanning-add-custom-pattern-details %}
|
||||
|
||||
After your pattern is created, {% data variables.product.prodname_secret_scanning %} scans for any secrets in {% ifversion fpt %}private{% endif %} repositories within your enterprise's organizations with {% data variables.product.prodname_GH_advanced_security %} enabled, including their entire Git history on all branches. Organization owners and repository administrators will be alerted to any secrets found, and can review the alert in the repository where the secret is found. For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
|
||||
|
||||
## Removing a custom pattern
|
||||
|
||||
Removing a custom pattern also closes all the {% data variables.product.prodname_secret_scanning %} alerts that the pattern created.
|
||||
1. Navigate to where the custom pattern was created. A custom pattern can be created in a repository, organization, or enterprise account.
|
||||
|
||||
1. Navigate to the **Security & analysis** settings for the repository or organization where the custom pattern was created. For more information, see "[Defining a custom pattern for a repository](#defining-a-custom-pattern-for-a-repository)" or "[Defining a custom pattern for an organization](#defining-a-custom-pattern-for-an-organization)" above.
|
||||
{% data reusables.repositories.navigate-to-ghas-settings %}
|
||||
1. Under "{% data variables.product.prodname_secret_scanning_caps %}", find the custom pattern you want to remove and click **Remove**.
|
||||
* For a repository or organization, it is the the **Security & analysis** settings for the repository or organization where the custom pattern was created. For more information, see "[Defining a custom pattern for a repository](#defining-a-custom-pattern-for-a-repository)" or "[Defining a custom pattern for an organization](#defining-a-custom-pattern-for-an-organization)" above.
|
||||
* For an enterprise, it is the **GitHub Advanced Security** settings for the enterprise where the custom pattern was created. For more information, see "[Defining a custom pattern for an enterprise account](#defining-a-custom-pattern-for-an-enterprise-account)" above.
|
||||
{%- ifversion fpt or ghes > 3.2 or ghae-next %}
|
||||
1. To the right of the custom pattern you want to remove, click {% octicon "trash" aria-label="The trash icon" %}.
|
||||
1. Review the confirmation, and select a method for dealing with any open alerts relating to the custom pattern.
|
||||
1. Click **Yes, delete this pattern**.
|
||||
|
||||
|
||||
1. Review the confirmation and click **Remove custom pattern**.
|
||||
|
||||
{%- elsif ghes = 3.2 %}
|
||||
1. To the right of the custom pattern you want to remove, click **Remove**.
|
||||
1. Review the confirmation, and click **Remove custom pattern**.
|
||||
{%- endif %}
|
||||
|
|
@ -23,9 +23,9 @@ This article explains how billing works for your codespaces, and explains how yo
|
|||
|
||||
Your organization's administrator might limit {% data variables.product.prodname_codespaces %} usage to only specific user accounts. To get access, you will need to contact your billing manager. For more information, see "[Managing access and security for your codespaces](/codespaces/managing-your-codespaces/managing-access-and-security-for-your-codespaces)."
|
||||
|
||||
## How spending limits work
|
||||
## How much it costs to use {% data variables.product.prodname_codespaces %}
|
||||
|
||||
Before your organization can use {% data variables.product.prodname_codespaces %}, your billing manager will need to set a spending limit. For more information, see "[Managing billing for Codespaces in your organization](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)."
|
||||
To see the pricing for {% data variables.product.prodname_codespaces %} usage, see "[{% data variables.product.prodname_codespaces %} pricing](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)."
|
||||
|
||||
## How your codespace usage is billed
|
||||
|
||||
|
|
@ -37,9 +37,13 @@ Your codespace is billed for the number of minutes that it's active. If your cod
|
|||
### Understanding how codespace storage is billed
|
||||
For {% data variables.product.prodname_codespaces %}, storage is defined to include any files relating to your codespace, such as the cloned repository, configuration files, and extensions, among others. This storage is billed while your codespace is shutdown. The storage billing for a codespace ends when you manually delete it from https://github.com/codespaces.
|
||||
|
||||
## How much it costs to use {% data variables.product.prodname_codespaces %}
|
||||
## How spending limits work
|
||||
|
||||
To see the pricing for {% data variables.product.prodname_codespaces %} usage, see "[{% data variables.product.prodname_codespaces %} pricing](/billing/managing-billing-for-github-codespaces/about-billing-for-codespaces#codespaces-pricing)."
|
||||
Before your organization can use {% data variables.product.prodname_codespaces %}, your billing manager will need to set a spending limit. For more information, see "[Managing spending limits for {% data variables.product.prodname_codespaces %}](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces)."
|
||||
|
||||
## Exporting changes when you have reached your spending limit
|
||||
|
||||
{% data reusables.codespaces.exporting-changes %}
|
||||
|
||||
## Checking your current usage and limits
|
||||
If you need to check your current usage or spending limit, contact your organization's billing manager. For more information, see "[Viewing your Codespaces usage](/billing/managing-billing-for-github-codespaces/viewing-your-codespaces-usage)."
|
||||
|
|
|
|||
|
|
@ -0,0 +1,27 @@
|
|||
---
|
||||
title: Exporting changes to a branch
|
||||
intro: 'This article provides steps for exporting your codespace changes to a branch.'
|
||||
product: '{% data reusables.gated-features.codespaces %}'
|
||||
versions:
|
||||
fpt: '*'
|
||||
type: reference
|
||||
topics:
|
||||
- Codespaces
|
||||
shortTitle: Exporting changes
|
||||
---
|
||||
|
||||
## Exporting changes to a branch
|
||||
|
||||
While using {% data variables.product.prodname_codespaces %}, you may want to export your changes to a branch without launching a your codespace.
|
||||
|
||||
This can be useful when you have hit a [spending limit](/billing/managing-billing-for-github-codespaces/managing-spending-limits-for-codespaces) or have a general issue accessing your codespace.
|
||||
|
||||
To export your changes:
|
||||
|
||||
1. Browse to the "Your Codespaces" page at [github.com/codespaces](https://github.com/codespaces) or, for an individual repository, click the **{% octicon "code" aria-label="The code icon" %} Code** menu.
|
||||
2. Click the ellipsis (**...**) to the right of the codespace you want to export from.
|
||||
3. Select **{% octicon "git-branch" aria-label="The git branch icon" %} Export changes to branch**.
|
||||
|
||||
|
||||
|
||||
4. From the popover, select **Create branch**.
|
||||
|
|
@ -11,12 +11,13 @@ redirect_from:
|
|||
- /github/developing-online-with-codespaces/troubleshooting-your-codespace
|
||||
- /codespaces/working-with-your-codespace/troubleshooting-your-codespace
|
||||
children:
|
||||
- /codespaces-logs
|
||||
- /exporting-changes-to-a-branch
|
||||
- /troubleshooting-creation-and-deletion-of-codespaces
|
||||
- /troubleshooting-your-connection-to-codespaces
|
||||
- /troubleshooting-dotfiles-for-codespaces
|
||||
- /troubleshooting-port-forwarding-for-codespaces
|
||||
- /troubleshooting-codespaces-clients
|
||||
- /codespaces-logs
|
||||
- /working-with-support-for-codespaces
|
||||
---
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ shortTitle: Connection
|
|||
|
||||
## 503 codespace service unavailable
|
||||
|
||||
Codespaces are set to stop after 30 mintues without any activity. If you try to interact with a codespace after it has stopped, you may see a `503 service unavailable` error.
|
||||
Codespaces are set to stop after 30 minutes without any activity. If you try to interact with a codespace after it has stopped, you may see a `503 service unavailable` error.
|
||||
|
||||
- If a **Start** button is shown in {% data variables.product.prodname_vscode %} or in your browser window, click **Start** to reconnect to the codespace.
|
||||
- Reset your codespace by reloading the window. From the [command palette](/codespaces/codespaces-reference/using-the-command-palette-in-codespaces#accessing-the-command-palette) in {% data variables.product.prodname_vscode %}, click **Developer: Reload Window**.
|
||||
|
|
|
|||
|
|
@ -298,8 +298,8 @@ To build this link, you'll need your OAuth Apps `client_id` that you received fr
|
|||
|
||||
* "[Troubleshooting authorization request errors](/apps/managing-oauth-apps/troubleshooting-authorization-request-errors)"
|
||||
* "[Troubleshooting OAuth App access token request errors](/apps/managing-oauth-apps/troubleshooting-oauth-app-access-token-request-errors)"
|
||||
{% ifversion fpt or ghae or ghes > 3.0 %}* "[Device flow errors](#error-codes-for-the-device-flow)"{% endif %}
|
||||
* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"
|
||||
{% ifversion fpt or ghae or ghes > 3.0 %}* "[Device flow errors](#error-codes-for-the-device-flow)"{% endif %}{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %}
|
||||
* "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
|
||||
|
||||
## Further reading
|
||||
|
||||
|
|
|
|||
|
|
@ -83,8 +83,8 @@ Keep these ideas in mind when using personal access tokens:
|
|||
* You can perform one-off cURL requests.
|
||||
* You can run personal scripts.
|
||||
* Don't set up a script for your whole team or company to use.
|
||||
* Don't set up a shared user account to act as a bot user.
|
||||
* Do set an expiration for your personal access tokens, to help keep your information secure.
|
||||
* Don't set up a shared user account to act as a bot user.{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 %}
|
||||
* Do set an expiration for your personal access tokens, to help keep your information secure.{% endif %}
|
||||
|
||||
## Determining which integration to build
|
||||
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ Personal access tokens (PATs) are an alternative to using passwords for authenti
|
|||
4. Click **Generate new token**.
|
||||
|
||||
5. Give your token a descriptive name.
|
||||
{% ifversion fpt or ghes > 3.1 or ghae-issue-4374 %}
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4374 %}
|
||||
6. To give your token an expiration, select the **Expiration** drop-down menu, then click a default or use the calendar picker.
|
||||
{% endif %}
|
||||
7. Select the scopes, or permissions, you'd like to grant this token. To use your token to access repositories from the command line, select **repo**.
|
||||
|
|
@ -76,5 +76,5 @@ Instead of manually entering your PAT for every HTTPS Git operation, you can cac
|
|||
|
||||
## Further reading
|
||||
|
||||
- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"
|
||||
- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"
|
||||
- "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)"{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %}
|
||||
- "[Token expiration and revocation](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation)"{% endif %}
|
||||
|
|
|
|||
|
|
@ -123,7 +123,7 @@ An overview of some of the most common actions that are recorded as events in th
|
|||
| Action | Description
|
||||
|------------------|-------------------
|
||||
| `create` | Triggered when you [grant access to an {% data variables.product.prodname_oauth_app %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/authorizing-oauth-apps).
|
||||
| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations) and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).
|
||||
| `destroy` | Triggered when you [revoke an {% data variables.product.prodname_oauth_app %}'s access to your account](/articles/reviewing-your-authorized-integrations){% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %} and when [authorizations are revoked or expire](/github/authenticating-to-github/keeping-your-account-and-data-secure/token-expiration-and-revocation).{% else %}.{% endif %}
|
||||
|
||||
{% ifversion fpt %}
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ topics:
|
|||
shortTitle: Token expiration
|
||||
---
|
||||
|
||||
When a token has expired or has been revoked, it can no longer be used to authenticate Git and API requests. It is not possible to restore an expired or revoked token, you or the application will need to create a new token.
|
||||
When a token {% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %}has expired or {% endif %} has been revoked, it can no longer be used to authenticate Git and API requests. It is not possible to restore an expired or revoked token, you or the application will need to create a new token.
|
||||
|
||||
This article explains the possible reasons your {% data variables.product.product_name %} token might be revoked or expire.
|
||||
|
||||
|
|
@ -21,7 +21,7 @@ This article explains the possible reasons your {% data variables.product.produc
|
|||
|
||||
{% endnote %}
|
||||
|
||||
{% ifversion fpt or ghae-issue-4374 or ghes > 3.1 %}
|
||||
{% ifversion fpt or ghae-issue-4374 or ghes > 3.2 %}
|
||||
## Token revoked after reaching its expiration date
|
||||
|
||||
When you create a personal access token, we recommend that you set an expiration for your token. Upon reaching your token's expiration date, the token is automatically revoked. For more information, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
|
||||
|
|
@ -55,8 +55,6 @@ The owner of an {% data variables.product.prodname_oauth_app %} can revoke an ac
|
|||
|
||||
{% data reusables.apps.oauth-token-limit %}
|
||||
|
||||
{% ifversion fpt or ghae or ghes > 3.1 %}
|
||||
## User token revoked due to {% data variables.product.prodname_github_app %} configuration
|
||||
|
||||
User-to-server tokens created by a {% data variables.product.prodname_github_app %} will expire after eight hours by default. Owners of {% data variables.product.prodname_github_apps %} can configure their apps so that user-to-server tokens do not expire. For more information about changing how your {% data variables.product.prodname_dotcom %} App's user-to-server tokens behave, see "[Activating optional features for apps](/developers/apps/getting-started-with-apps/activating-optional-features-for-apps)."
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -0,0 +1,28 @@
|
|||
---
|
||||
title: Customizing your organization's profile
|
||||
intro: You can share information about your organization by customizing your organization's profile
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghes: '*'
|
||||
ghae: '*'
|
||||
topics:
|
||||
- Organizations
|
||||
shortTitle: Customize organization profile
|
||||
---
|
||||
|
||||
## About your organization's profile README
|
||||
|
||||
You can share information about how to engage with your organization by creating an organization profile README. {% data variables.product.prodname_dotcom %} shows your organization profile README in the "Overview" tab of your organization.
|
||||
|
||||
You can choose what information to include your organization profile README. Here are some examples of information that may be helpful in your organization's profile README.
|
||||
|
||||
- An "About" section that describes your organization
|
||||
- Guidance for getting help in the organization
|
||||
|
||||
You can format text and include emoji, images, and GIFs in your organization profile README by using {% data variables.product.company_short %} Flavored Markdown. For more information, see "[Getting started with writing and formatting on {% data variables.product.prodname_dotcom %}](/github/writing-on-github/getting-started-with-writing-and-formatting-on-github)."
|
||||
|
||||
## Adding an organization profile README
|
||||
|
||||
1. If your organization does not already have a public `.github` repository, create a public `.github` repository.
|
||||
2. In your organization's `.github` repository, create a `README.md` file in the `profile` folder.
|
||||
3. Commit the changes to the `README.md` file. The content of the `README.md` will appear on your organization's profile.
|
||||
|
|
@ -17,6 +17,7 @@ children:
|
|||
- /about-your-organization-dashboard
|
||||
- /creating-a-new-organization-from-scratch
|
||||
- /accessing-your-organizations-settings
|
||||
- /customizing-your-organizations-profile
|
||||
- /about-your-organizations-news-feed
|
||||
- /viewing-insights-for-your-organization
|
||||
shortTitle: Collaborate with groups
|
||||
|
|
|
|||
|
|
@ -72,26 +72,42 @@ To set up an apex domain, such as `example.com`, you must configure a _CNAME_ fi
|
|||
{% data reusables.pages.sidebar-pages %}
|
||||
4. Under "Custom domain", type your custom domain, then click **Save**. This will create a commit that adds a _CNAME_ file in the root of your publishing source.
|
||||
|
||||
5. Navigate to your DNS provider and create either an `ALIAS`, `ANAME`, or `A` record. {% data reusables.pages.contact-dns-provider %}
|
||||
5. Navigate to your DNS provider and create either an `ALIAS`, `ANAME`, or `A` record. You can also create `AAAA` records for IPv6 support. {% data reusables.pages.contact-dns-provider %}
|
||||
- To create an `ALIAS` or `ANAME` record, point your apex domain to the default domain for your site. {% data reusables.pages.default-domain-information %}
|
||||
- To create `A` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
|
||||
- To create `A` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
|
||||
```shell
|
||||
185.199.108.153
|
||||
185.199.109.153
|
||||
185.199.110.153
|
||||
185.199.111.153
|
||||
```
|
||||
- To create `AAAA` records, point your apex domain to the IP addresses for {% data variables.product.prodname_pages %}.
|
||||
```shell
|
||||
2606:50c0:8000::153
|
||||
2606:50c0:8001::153
|
||||
2606:50c0:8002::153
|
||||
2606:50c0:8003::153
|
||||
```
|
||||
|
||||
{% indented_data_reference reusables.pages.wildcard-dns-warning spaces=3 %}
|
||||
{% data reusables.command_line.open_the_multi_os_terminal %}
|
||||
6. To confirm that your DNS record configured correctly, use the `dig` command, replacing _EXAMPLE.COM_ with your apex domain. Confirm that the results match the IP addresses for {% data variables.product.prodname_pages %} above.
|
||||
```shell
|
||||
$ dig <em>EXAMPLE.COM</em> +noall +answer
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.108.153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.109.153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.110.153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.111.153
|
||||
```
|
||||
- For `A` records.
|
||||
```shell
|
||||
$ dig <em>EXAMPLE.COM</em> +noall +answer -t A
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.108.153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.109.153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.110.153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN A 185.199.111.153
|
||||
```
|
||||
- For `AAAA` records.
|
||||
```shell
|
||||
$ dig <em>EXAMPLE.COM</em> +noall +answer -t AAAA
|
||||
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8000::153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8001::153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8002::153
|
||||
> <em>EXAMPLE.COM</em> 3600 IN AAAA 2606:50c0:8003::153
|
||||
```
|
||||
{% data reusables.pages.build-locally-download-cname %}
|
||||
{% data reusables.pages.enforce-https-custom-domain %}
|
||||
|
||||
|
|
|
|||
|
|
@ -94,7 +94,7 @@ Text files over **5 MB** are only available through their raw URLs, which are se
|
|||
Because diffs can become very large, we impose these limits on diffs for commits, pull requests, and compare views:
|
||||
|
||||
- In a pull request, no total diff may exceed *20,000 lines that you can load* or *1 MB* of raw diff data.
|
||||
- No single file's diff may exceed *3,000 lines that you can load* or *100 KB* of raw diff data. *Four hundred lines* and *20 KB* are automatically loaded for a single file.
|
||||
- No single file's diff may exceed *20,000 lines that you can load* or *500 KB* of raw diff data. *Four hundred lines* and *20 KB* are automatically loaded for a single file.
|
||||
- The maximum number of files in a single diff is limited to *300*.
|
||||
- The maximum number of renderable files (such as images, PDFs, and GeoJSON files) in a single diff is limited to *25*.
|
||||
|
||||
|
|
|
|||
|
|
@ -43,7 +43,7 @@ The Actions workflow progress can be viewed (by GitHub employees) in the [Action
|
|||
|
||||
## Manually triggering the search index update workflow
|
||||
|
||||
You can manually run the workflow to generate the indexes after you push your changes to `main` to speed up the indexing when needed. To run it manually, click "Run workflow" button in the [Actions tab](https://github.com/github/docs-internal/actions/workflows/sync-search-indices.yml).
|
||||
You can manually run the workflow to generate the indexes after you push your changes to `main` to speed up the indexing when needed. It's recommended to do this for only the `free-pro-team@latest` version and the `en` language because running all languages and versions take about 40 minutes. To run it manually, click "Run workflow" button in the [Actions tab](https://github.com/github/docs-internal/actions/workflows/sync-search-indices.yml). Enter the language and version you'd like to generate the indexes for as inputs to the workflow. By default, all language and versions are generated.
|
||||
|
||||
## Generating search indexes for your local checkout
|
||||
|
||||
|
|
|
|||
|
|
@ -4270,6 +4270,19 @@ qualified).
|
|||
|
||||
The Ref may be specified by its global node ID or by the
|
||||
repository nameWithOwner and branch name.
|
||||
|
||||
### Examples
|
||||
|
||||
Specify a branch using a global node ID:
|
||||
|
||||
{ "id": "MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=" }
|
||||
|
||||
Specify a branch using nameWithOwner and branch name:
|
||||
|
||||
{
|
||||
"nameWithOwner": "github/graphql-client",
|
||||
"branchName": "main"
|
||||
}
|
||||
"""
|
||||
input CommittableBranch {
|
||||
"""
|
||||
|
|
@ -11758,7 +11771,7 @@ slash-prefixed.
|
|||
`path` values must be unique across all `additions` and `deletions`
|
||||
provided. Any duplication will result in a validation error.
|
||||
|
||||
## Encoding
|
||||
### Encoding
|
||||
|
||||
File contents must be provided in full for each `FileAddition`.
|
||||
|
||||
|
|
@ -11778,7 +11791,7 @@ and ensuring that all files in a repository use a consistent
|
|||
line-ending convention (`\n` or `\r\n`), and that all files end
|
||||
with a newline.
|
||||
|
||||
## Modeling file changes
|
||||
### Modeling file changes
|
||||
|
||||
Each of the the five types of conceptual changes that can be made in a
|
||||
git commit can be described using the `FileChanges` type as follows:
|
||||
|
|
@ -16537,7 +16550,7 @@ type Mutation {
|
|||
branch and also updates that branch to point to the new commit.
|
||||
It can be thought of as similar to `git commit`.
|
||||
|
||||
## Locating a Branch
|
||||
### Locating a Branch
|
||||
|
||||
Commits are appended to a `branch` of type `Ref`.
|
||||
This must refer to a git branch (i.e. the fully qualified path must
|
||||
|
|
@ -16547,7 +16560,7 @@ type Mutation {
|
|||
ID or by passing both of `repositoryNameWithOwner` and `refName`. For
|
||||
more details see the documentation for `CommittableBranch`.
|
||||
|
||||
## Describing Changes
|
||||
### Describing Changes
|
||||
|
||||
`fileChanges` are specified as a `FilesChanges` object describing
|
||||
`FileAdditions` and `FileDeletions`.
|
||||
|
|
@ -16555,7 +16568,7 @@ type Mutation {
|
|||
Please see the documentation for `FileChanges` for more information on
|
||||
how to use this argument to describe any set of file changes.
|
||||
|
||||
## Authorship
|
||||
### Authorship
|
||||
|
||||
Similar to the web commit interface, this mutation does not support
|
||||
specifying the author or committer of the commit and will not add
|
||||
|
|
@ -16569,7 +16582,7 @@ type Mutation {
|
|||
If you need full control over author and committer information, please
|
||||
use the Git Database REST API instead.
|
||||
|
||||
## Commit Signing
|
||||
### Commit Signing
|
||||
|
||||
Commits made using this mutation are automatically signed by GitHub if
|
||||
supported and will be marked as verified in the user interface.
|
||||
|
|
|
|||
|
|
@ -4472,6 +4472,19 @@ qualified).
|
|||
|
||||
The Ref may be specified by its global node ID or by the
|
||||
repository nameWithOwner and branch name.
|
||||
|
||||
### Examples
|
||||
|
||||
Specify a branch using a global node ID:
|
||||
|
||||
{ "id": "MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=" }
|
||||
|
||||
Specify a branch using nameWithOwner and branch name:
|
||||
|
||||
{
|
||||
"nameWithOwner": "github/graphql-client",
|
||||
"branchName": "main"
|
||||
}
|
||||
"""
|
||||
input CommittableBranch {
|
||||
"""
|
||||
|
|
@ -12496,7 +12509,7 @@ slash-prefixed.
|
|||
`path` values must be unique across all `additions` and `deletions`
|
||||
provided. Any duplication will result in a validation error.
|
||||
|
||||
## Encoding
|
||||
### Encoding
|
||||
|
||||
File contents must be provided in full for each `FileAddition`.
|
||||
|
||||
|
|
@ -12516,7 +12529,7 @@ and ensuring that all files in a repository use a consistent
|
|||
line-ending convention (`\n` or `\r\n`), and that all files end
|
||||
with a newline.
|
||||
|
||||
## Modeling file changes
|
||||
### Modeling file changes
|
||||
|
||||
Each of the the five types of conceptual changes that can be made in a
|
||||
git commit can be described using the `FileChanges` type as follows:
|
||||
|
|
@ -17854,7 +17867,7 @@ type Mutation {
|
|||
branch and also updates that branch to point to the new commit.
|
||||
It can be thought of as similar to `git commit`.
|
||||
|
||||
## Locating a Branch
|
||||
### Locating a Branch
|
||||
|
||||
Commits are appended to a `branch` of type `Ref`.
|
||||
This must refer to a git branch (i.e. the fully qualified path must
|
||||
|
|
@ -17864,7 +17877,7 @@ type Mutation {
|
|||
ID or by passing both of `repositoryNameWithOwner` and `refName`. For
|
||||
more details see the documentation for `CommittableBranch`.
|
||||
|
||||
## Describing Changes
|
||||
### Describing Changes
|
||||
|
||||
`fileChanges` are specified as a `FilesChanges` object describing
|
||||
`FileAdditions` and `FileDeletions`.
|
||||
|
|
@ -17872,7 +17885,7 @@ type Mutation {
|
|||
Please see the documentation for `FileChanges` for more information on
|
||||
how to use this argument to describe any set of file changes.
|
||||
|
||||
## Authorship
|
||||
### Authorship
|
||||
|
||||
Similar to the web commit interface, this mutation does not support
|
||||
specifying the author or committer of the commit and will not add
|
||||
|
|
@ -17886,7 +17899,7 @@ type Mutation {
|
|||
If you need full control over author and committer information, please
|
||||
use the Git Database REST API instead.
|
||||
|
||||
## Commit Signing
|
||||
### Commit Signing
|
||||
|
||||
Commits made using this mutation are automatically signed by GitHub if
|
||||
supported and will be marked as verified in the user interface.
|
||||
|
|
|
|||
|
|
@ -83,12 +83,6 @@ sections:
|
|||
|
||||
The different token types now have unique identifiable prefixes, which allows for secret scanning to detect the tokens so that you can mitigate the impact of someone accidentally committing a token to a repository. {% data variables.product.company_short %} recommends updating existing tokens as soon as possible. For more information, see "[About authentication to {% data variables.product.prodname_dotcom %}](/github/authenticating-to-github/keeping-your-account-and-data-secure/about-authentication-to-github#githubs-token-formats)" and "[About {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/about-secret-scanning)."
|
||||
|
||||
# https://github.com/github/releases/issues/1390
|
||||
- |
|
||||
An expiration date can now be set for new and existing personal access tokens. Setting an expiration date on personal access tokens is highly recommended to prevent older tokens from leaking and compromising security. Token owners will receive an email when it's time to renew a token that's about to expire. Tokens that have expired can be regenerated, giving users a duplicate token with the same properties as the original.
|
||||
|
||||
When using a personal access token with the {% data variables.product.company_short %} API, a new `GitHub-Authentication-Token-Expiration` header is included in the response, which indicates the token's expiration date. For more information, see "[Creating a personal access token](/github/authenticating-to-github/keeping-your-account-and-data-secure/creating-a-personal-access-token)."
|
||||
|
||||
- heading: 'Repositories changes'
|
||||
notes:
|
||||
# https://github.com/github/releases/issues/1295
|
||||
|
|
|
|||
|
|
@ -1,10 +1,7 @@
|
|||
1. Under "{% data variables.product.prodname_secret_scanning_caps %}", click **Add a {% data variables.product.prodname_secret_scanning %} custom pattern**.
|
||||
|
||||
|
||||
1. Enter the details for your new custom pattern:
|
||||
1. You must at least provide the name for your pattern, and a regular expression for the format of your secret pattern.
|
||||
1. You can click **More options {% octicon "chevron-down" aria-label="down" %}** to provide other surrounding content or additional match requirements for the secret format.
|
||||
1. You can provide a sample test string to make sure your configuration is matching the patterns you expect.
|
||||
1. Provide a sample test string to make sure your configuration is matching the patterns you expect.
|
||||
|
||||
|
||||
1. When you are satisfied with your new custom pattern, click **Create custom pattern**.
|
||||
1. When you are satisfied with your new custom pattern, click {% ifversion fpt or ghes > 3.2 or ghae-next %}**Create pattern**{% elsif ghes = 3.2 %}**Create custom pattern**{% endif %}.
|
||||
|
|
@ -0,0 +1 @@
|
|||
1. Under "{% data variables.product.prodname_secret_scanning_caps %}", under "Custom patterns", click {% ifversion fpt or ghes > 3.2 or ghae-next %}**New pattern**{% elsif ghes = 3.2 %}**New custom pattern**{% endif %}.
|
||||
|
|
@ -0,0 +1 @@
|
|||
If you hit a spending limit, you will no longer be able to create or resume your codespaces. You can still [export any work in progress changes to a new branch](/codespaces/troubleshooting/exporting-changes-to-a-branch).
|
||||
|
|
@ -0,0 +1 @@
|
|||
1. Under "GitHub Advanced Security", click the **Security features** tab.
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
Partner | Supported secret | API slug
|
||||
Provider | Supported secret | API slug
|
||||
--- | --- | ---
|
||||
{%- ifversion fpt or ghes > 2.22 or ghae-next %}
|
||||
Adafruit IO | Adafruit IO Key | adafruit_io_key{% endif %}
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
For a list of supported regions, see [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors#countries).
|
||||
For a list of supported regions, see [{% data variables.product.prodname_sponsors %}](https://github.com/sponsors#regions).
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
| C# {% ifversion fpt %}| {% octicon "x" aria-label="The X icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% endif %}
|
||||
| C# {% ifversion fpt %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif ghes %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% elsif ghae %}| {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %} | {% octicon "check" aria-label="The check icon" %}<br>`dotnet` CLI |{% endif %}
|
||||
|
|
|
|||
Различия файлов скрыты, потому что одна или несколько строк слишком длинны
|
|
@ -2002,7 +2002,7 @@
|
|||
"kind": "mutations",
|
||||
"id": "createcommitonbranch",
|
||||
"href": "/graphql/reference/mutations#createcommitonbranch",
|
||||
"description": "<p>Appends a commit to the given branch as the authenticated user.</p>\n<p>This mutation creates a commit whose parent is the HEAD of the provided\nbranch and also updates that branch to point to the new commit.\nIt can be thought of as similar to <code>git commit</code>.</p>\n<h2 id=\"locating-a-branch\"><a href=\"#locating-a-branch\">Locating a Branch</a></h2>\n<p>Commits are appended to a <code>branch</code> of type <code>Ref</code>.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with <code>refs/heads/</code>, although including this prefix is optional.</p>\n<p>Callers may specify the <code>branch</code> to commit to either by its global node\nID or by passing both of <code>repositoryNameWithOwner</code> and <code>refName</code>. For\nmore details see the documentation for <code>CommittableBranch</code>.</p>\n<h2 id=\"describing-changes\"><a href=\"#describing-changes\">Describing Changes</a></h2>\n<p><code>fileChanges</code> are specified as a <code>FilesChanges</code> object describing\n<code>FileAdditions</code> and <code>FileDeletions</code>.</p>\n<p>Please see the documentation for <code>FileChanges</code> for more information on\nhow to use this argument to describe any set of file changes.</p>\n<h2 id=\"authorship\"><a href=\"#authorship\">Authorship</a></h2>\n<p>Similar to the web commit interface, this mutation does not support\nspecifying the author or committer of the commit and will not add\nsupport for this in the future.</p>\n<p>A commit created by a successful execution of this mutation will be\nauthored by the owner of the credential which authenticates the API\nrequest. The committer will be identical to that of commits authored\nusing the web interface.</p>\n<p>If you need full control over author and committer information, please\nuse the Git Database REST API instead.</p>\n<h2 id=\"commit-signing\"><a href=\"#commit-signing\">Commit Signing</a></h2>\n<p>Commits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.</p>",
|
||||
"description": "<p>Appends a commit to the given branch as the authenticated user.</p>\n<p>This mutation creates a commit whose parent is the HEAD of the provided\nbranch and also updates that branch to point to the new commit.\nIt can be thought of as similar to <code>git commit</code>.</p>\n<h3 id=\"locating-a-branch\"><a href=\"#locating-a-branch\">Locating a Branch</a></h3>\n<p>Commits are appended to a <code>branch</code> of type <code>Ref</code>.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with <code>refs/heads/</code>, although including this prefix is optional.</p>\n<p>Callers may specify the <code>branch</code> to commit to either by its global node\nID or by passing both of <code>repositoryNameWithOwner</code> and <code>refName</code>. For\nmore details see the documentation for <code>CommittableBranch</code>.</p>\n<h3 id=\"describing-changes\"><a href=\"#describing-changes\">Describing Changes</a></h3>\n<p><code>fileChanges</code> are specified as a <code>FilesChanges</code> object describing\n<code>FileAdditions</code> and <code>FileDeletions</code>.</p>\n<p>Please see the documentation for <code>FileChanges</code> for more information on\nhow to use this argument to describe any set of file changes.</p>\n<h3 id=\"authorship\"><a href=\"#authorship\">Authorship</a></h3>\n<p>Similar to the web commit interface, this mutation does not support\nspecifying the author or committer of the commit and will not add\nsupport for this in the future.</p>\n<p>A commit created by a successful execution of this mutation will be\nauthored by the owner of the credential which authenticates the API\nrequest. The committer will be identical to that of commits authored\nusing the web interface.</p>\n<p>If you need full control over author and committer information, please\nuse the Git Database REST API instead.</p>\n<h3 id=\"commit-signing\"><a href=\"#commit-signing\">Commit Signing</a></h3>\n<p>Commits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.</p>",
|
||||
"inputFields": [
|
||||
{
|
||||
"name": "input",
|
||||
|
|
@ -71467,7 +71467,7 @@
|
|||
"kind": "inputObjects",
|
||||
"id": "committablebranch",
|
||||
"href": "/graphql/reference/input-objects#committablebranch",
|
||||
"description": "<p>A git ref for a commit to be appended to.</p>\n<p>The ref must be a branch, i.e. its fully qualified name must start\nwith <code>refs/heads/</code> (although the input is not required to be fully\nqualified).</p>\n<p>The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.</p>",
|
||||
"description": "<p>A git ref for a commit to be appended to.</p>\n<p>The ref must be a branch, i.e. its fully qualified name must start\nwith <code>refs/heads/</code> (although the input is not required to be fully\nqualified).</p>\n<p>The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.</p>\n<h3 id=\"examples\"><a href=\"#examples\">Examples</a></h3>\n<p>Specify a branch using a global node ID:</p>\n<pre><code>{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\n</code></pre>\n<p>Specify a branch using nameWithOwner and branch name:</p>\n<pre><code>{\n \"nameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\n</code></pre>",
|
||||
"inputFields": [
|
||||
{
|
||||
"name": "branchName",
|
||||
|
|
@ -73956,7 +73956,7 @@
|
|||
"kind": "inputObjects",
|
||||
"id": "filechanges",
|
||||
"href": "/graphql/reference/input-objects#filechanges",
|
||||
"description": "<p>A description of a set of changes to a file tree to be made as part of\na git commit, modeled as zero or more file <code>additions</code> and zero or more\nfile <code>deletions</code>.</p>\n<p>Both fields are optional; omitting both will produce a commit with no\nfile changes.</p>\n<p><code>deletions</code> and <code>additions</code> describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n<code>/</code>. The root of a git tree is an empty string, so paths are not\nslash-prefixed.</p>\n<p><code>path</code> values must be unique across all <code>additions</code> and <code>deletions</code>\nprovided. Any duplication will result in a validation error.</p>\n<h2 id=\"encoding\"><a href=\"#encoding\">Encoding</a></h2>\n<p>File contents must be provided in full for each <code>FileAddition</code>.</p>\n<p>The <code>contents</code> of a <code>FileAddition</code> must be encoded using RFC 4648\ncompliant base64, i.e. correct padding is required and no characters\noutside the standard alphabet may be used. Invalid base64\nencoding will be rejected with a validation error.</p>\n<p>The encoded contents may be binary.</p>\n<p>For text files, no assumptions are made about the character encoding of\nthe file contents (after base64 decoding). No charset transcoding or\nline-ending normalization will be performed; it is the client's\nresponsibility to manage the character encoding of files they provide.\nHowever, for maximum compatibility we recommend using UTF-8 encoding\nand ensuring that all files in a repository use a consistent\nline-ending convention (<code>\\n</code> or <code>\\r\\n</code>), and that all files end\nwith a newline.</p>\n<h2 id=\"modeling-file-changes\"><a href=\"#modeling-file-changes\">Modeling file changes</a></h2>\n<p>Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the <code>FileChanges</code> type as follows:</p>\n<ol>\n<li>\n<p>New file addition: create file <code>hello world\\n</code> at path <code>docs/README.txt</code>:</p>\n<p> {\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}</p>\n</li>\n<li>\n<p>Existing file modification: change existing <code>docs/README.txt</code> to have new\ncontent <code>new content here\\n</code>:</p>\n<pre><code>{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>Existing file deletion: remove existing file <code>docs/README.txt</code>.\nNote that the path is required to exist -- specifying a\npath that does not exist on the given branch will abort the\ncommit and return an error.</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with no changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to the same content at\n<code>newdocs/README.txt</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"hello world\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to a file at path\n<code>newdocs/README.txt</code> with content <code>new contents\\n</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"new contents\\n\")\n }\n ]\n}.\n</code></pre>\n</li>\n</ol>",
|
||||
"description": "<p>A description of a set of changes to a file tree to be made as part of\na git commit, modeled as zero or more file <code>additions</code> and zero or more\nfile <code>deletions</code>.</p>\n<p>Both fields are optional; omitting both will produce a commit with no\nfile changes.</p>\n<p><code>deletions</code> and <code>additions</code> describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n<code>/</code>. The root of a git tree is an empty string, so paths are not\nslash-prefixed.</p>\n<p><code>path</code> values must be unique across all <code>additions</code> and <code>deletions</code>\nprovided. Any duplication will result in a validation error.</p>\n<h3 id=\"encoding\"><a href=\"#encoding\">Encoding</a></h3>\n<p>File contents must be provided in full for each <code>FileAddition</code>.</p>\n<p>The <code>contents</code> of a <code>FileAddition</code> must be encoded using RFC 4648\ncompliant base64, i.e. correct padding is required and no characters\noutside the standard alphabet may be used. Invalid base64\nencoding will be rejected with a validation error.</p>\n<p>The encoded contents may be binary.</p>\n<p>For text files, no assumptions are made about the character encoding of\nthe file contents (after base64 decoding). No charset transcoding or\nline-ending normalization will be performed; it is the client's\nresponsibility to manage the character encoding of files they provide.\nHowever, for maximum compatibility we recommend using UTF-8 encoding\nand ensuring that all files in a repository use a consistent\nline-ending convention (<code>\\n</code> or <code>\\r\\n</code>), and that all files end\nwith a newline.</p>\n<h3 id=\"modeling-file-changes\"><a href=\"#modeling-file-changes\">Modeling file changes</a></h3>\n<p>Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the <code>FileChanges</code> type as follows:</p>\n<ol>\n<li>\n<p>New file addition: create file <code>hello world\\n</code> at path <code>docs/README.txt</code>:</p>\n<p> {\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}</p>\n</li>\n<li>\n<p>Existing file modification: change existing <code>docs/README.txt</code> to have new\ncontent <code>new content here\\n</code>:</p>\n<pre><code>{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>Existing file deletion: remove existing file <code>docs/README.txt</code>.\nNote that the path is required to exist -- specifying a\npath that does not exist on the given branch will abort the\ncommit and return an error.</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with no changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to the same content at\n<code>newdocs/README.txt</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"hello world\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to a file at path\n<code>newdocs/README.txt</code> with content <code>new contents\\n</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"new contents\\n\")\n }\n ]\n}.\n</code></pre>\n</li>\n</ol>",
|
||||
"inputFields": [
|
||||
{
|
||||
"name": "additions",
|
||||
|
|
|
|||
|
|
@ -1545,7 +1545,7 @@
|
|||
"kind": "mutations",
|
||||
"id": "createcommitonbranch",
|
||||
"href": "/graphql/reference/mutations#createcommitonbranch",
|
||||
"description": "<p>Appends a commit to the given branch as the authenticated user.</p>\n<p>This mutation creates a commit whose parent is the HEAD of the provided\nbranch and also updates that branch to point to the new commit.\nIt can be thought of as similar to <code>git commit</code>.</p>\n<h2 id=\"locating-a-branch\"><a href=\"#locating-a-branch\">Locating a Branch</a></h2>\n<p>Commits are appended to a <code>branch</code> of type <code>Ref</code>.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with <code>refs/heads/</code>, although including this prefix is optional.</p>\n<p>Callers may specify the <code>branch</code> to commit to either by its global node\nID or by passing both of <code>repositoryNameWithOwner</code> and <code>refName</code>. For\nmore details see the documentation for <code>CommittableBranch</code>.</p>\n<h2 id=\"describing-changes\"><a href=\"#describing-changes\">Describing Changes</a></h2>\n<p><code>fileChanges</code> are specified as a <code>FilesChanges</code> object describing\n<code>FileAdditions</code> and <code>FileDeletions</code>.</p>\n<p>Please see the documentation for <code>FileChanges</code> for more information on\nhow to use this argument to describe any set of file changes.</p>\n<h2 id=\"authorship\"><a href=\"#authorship\">Authorship</a></h2>\n<p>Similar to the web commit interface, this mutation does not support\nspecifying the author or committer of the commit and will not add\nsupport for this in the future.</p>\n<p>A commit created by a successful execution of this mutation will be\nauthored by the owner of the credential which authenticates the API\nrequest. The committer will be identical to that of commits authored\nusing the web interface.</p>\n<p>If you need full control over author and committer information, please\nuse the Git Database REST API instead.</p>\n<h2 id=\"commit-signing\"><a href=\"#commit-signing\">Commit Signing</a></h2>\n<p>Commits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.</p>",
|
||||
"description": "<p>Appends a commit to the given branch as the authenticated user.</p>\n<p>This mutation creates a commit whose parent is the HEAD of the provided\nbranch and also updates that branch to point to the new commit.\nIt can be thought of as similar to <code>git commit</code>.</p>\n<h3 id=\"locating-a-branch\"><a href=\"#locating-a-branch\">Locating a Branch</a></h3>\n<p>Commits are appended to a <code>branch</code> of type <code>Ref</code>.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with <code>refs/heads/</code>, although including this prefix is optional.</p>\n<p>Callers may specify the <code>branch</code> to commit to either by its global node\nID or by passing both of <code>repositoryNameWithOwner</code> and <code>refName</code>. For\nmore details see the documentation for <code>CommittableBranch</code>.</p>\n<h3 id=\"describing-changes\"><a href=\"#describing-changes\">Describing Changes</a></h3>\n<p><code>fileChanges</code> are specified as a <code>FilesChanges</code> object describing\n<code>FileAdditions</code> and <code>FileDeletions</code>.</p>\n<p>Please see the documentation for <code>FileChanges</code> for more information on\nhow to use this argument to describe any set of file changes.</p>\n<h3 id=\"authorship\"><a href=\"#authorship\">Authorship</a></h3>\n<p>Similar to the web commit interface, this mutation does not support\nspecifying the author or committer of the commit and will not add\nsupport for this in the future.</p>\n<p>A commit created by a successful execution of this mutation will be\nauthored by the owner of the credential which authenticates the API\nrequest. The committer will be identical to that of commits authored\nusing the web interface.</p>\n<p>If you need full control over author and committer information, please\nuse the Git Database REST API instead.</p>\n<h3 id=\"commit-signing\"><a href=\"#commit-signing\">Commit Signing</a></h3>\n<p>Commits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.</p>",
|
||||
"inputFields": [
|
||||
{
|
||||
"name": "input",
|
||||
|
|
@ -64290,7 +64290,7 @@
|
|||
"kind": "inputObjects",
|
||||
"id": "committablebranch",
|
||||
"href": "/graphql/reference/input-objects#committablebranch",
|
||||
"description": "<p>A git ref for a commit to be appended to.</p>\n<p>The ref must be a branch, i.e. its fully qualified name must start\nwith <code>refs/heads/</code> (although the input is not required to be fully\nqualified).</p>\n<p>The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.</p>",
|
||||
"description": "<p>A git ref for a commit to be appended to.</p>\n<p>The ref must be a branch, i.e. its fully qualified name must start\nwith <code>refs/heads/</code> (although the input is not required to be fully\nqualified).</p>\n<p>The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.</p>\n<h3 id=\"examples\"><a href=\"#examples\">Examples</a></h3>\n<p>Specify a branch using a global node ID:</p>\n<pre><code>{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\n</code></pre>\n<p>Specify a branch using nameWithOwner and branch name:</p>\n<pre><code>{\n \"nameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\n</code></pre>",
|
||||
"inputFields": [
|
||||
{
|
||||
"name": "branchName",
|
||||
|
|
@ -66568,7 +66568,7 @@
|
|||
"kind": "inputObjects",
|
||||
"id": "filechanges",
|
||||
"href": "/graphql/reference/input-objects#filechanges",
|
||||
"description": "<p>A description of a set of changes to a file tree to be made as part of\na git commit, modeled as zero or more file <code>additions</code> and zero or more\nfile <code>deletions</code>.</p>\n<p>Both fields are optional; omitting both will produce a commit with no\nfile changes.</p>\n<p><code>deletions</code> and <code>additions</code> describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n<code>/</code>. The root of a git tree is an empty string, so paths are not\nslash-prefixed.</p>\n<p><code>path</code> values must be unique across all <code>additions</code> and <code>deletions</code>\nprovided. Any duplication will result in a validation error.</p>\n<h2 id=\"encoding\"><a href=\"#encoding\">Encoding</a></h2>\n<p>File contents must be provided in full for each <code>FileAddition</code>.</p>\n<p>The <code>contents</code> of a <code>FileAddition</code> must be encoded using RFC 4648\ncompliant base64, i.e. correct padding is required and no characters\noutside the standard alphabet may be used. Invalid base64\nencoding will be rejected with a validation error.</p>\n<p>The encoded contents may be binary.</p>\n<p>For text files, no assumptions are made about the character encoding of\nthe file contents (after base64 decoding). No charset transcoding or\nline-ending normalization will be performed; it is the client's\nresponsibility to manage the character encoding of files they provide.\nHowever, for maximum compatibility we recommend using UTF-8 encoding\nand ensuring that all files in a repository use a consistent\nline-ending convention (<code>\\n</code> or <code>\\r\\n</code>), and that all files end\nwith a newline.</p>\n<h2 id=\"modeling-file-changes\"><a href=\"#modeling-file-changes\">Modeling file changes</a></h2>\n<p>Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the <code>FileChanges</code> type as follows:</p>\n<ol>\n<li>\n<p>New file addition: create file <code>hello world\\n</code> at path <code>docs/README.txt</code>:</p>\n<p> {\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}</p>\n</li>\n<li>\n<p>Existing file modification: change existing <code>docs/README.txt</code> to have new\ncontent <code>new content here\\n</code>:</p>\n<pre><code>{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>Existing file deletion: remove existing file <code>docs/README.txt</code>.\nNote that the path is required to exist -- specifying a\npath that does not exist on the given branch will abort the\ncommit and return an error.</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with no changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to the same content at\n<code>newdocs/README.txt</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"hello world\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to a file at path\n<code>newdocs/README.txt</code> with content <code>new contents\\n</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"new contents\\n\")\n }\n ]\n}.\n</code></pre>\n</li>\n</ol>",
|
||||
"description": "<p>A description of a set of changes to a file tree to be made as part of\na git commit, modeled as zero or more file <code>additions</code> and zero or more\nfile <code>deletions</code>.</p>\n<p>Both fields are optional; omitting both will produce a commit with no\nfile changes.</p>\n<p><code>deletions</code> and <code>additions</code> describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n<code>/</code>. The root of a git tree is an empty string, so paths are not\nslash-prefixed.</p>\n<p><code>path</code> values must be unique across all <code>additions</code> and <code>deletions</code>\nprovided. Any duplication will result in a validation error.</p>\n<h3 id=\"encoding\"><a href=\"#encoding\">Encoding</a></h3>\n<p>File contents must be provided in full for each <code>FileAddition</code>.</p>\n<p>The <code>contents</code> of a <code>FileAddition</code> must be encoded using RFC 4648\ncompliant base64, i.e. correct padding is required and no characters\noutside the standard alphabet may be used. Invalid base64\nencoding will be rejected with a validation error.</p>\n<p>The encoded contents may be binary.</p>\n<p>For text files, no assumptions are made about the character encoding of\nthe file contents (after base64 decoding). No charset transcoding or\nline-ending normalization will be performed; it is the client's\nresponsibility to manage the character encoding of files they provide.\nHowever, for maximum compatibility we recommend using UTF-8 encoding\nand ensuring that all files in a repository use a consistent\nline-ending convention (<code>\\n</code> or <code>\\r\\n</code>), and that all files end\nwith a newline.</p>\n<h3 id=\"modeling-file-changes\"><a href=\"#modeling-file-changes\">Modeling file changes</a></h3>\n<p>Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the <code>FileChanges</code> type as follows:</p>\n<ol>\n<li>\n<p>New file addition: create file <code>hello world\\n</code> at path <code>docs/README.txt</code>:</p>\n<p> {\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}</p>\n</li>\n<li>\n<p>Existing file modification: change existing <code>docs/README.txt</code> to have new\ncontent <code>new content here\\n</code>:</p>\n<pre><code>{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>Existing file deletion: remove existing file <code>docs/README.txt</code>.\nNote that the path is required to exist -- specifying a\npath that does not exist on the given branch will abort the\ncommit and return an error.</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with no changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to the same content at\n<code>newdocs/README.txt</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"hello world\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to a file at path\n<code>newdocs/README.txt</code> with content <code>new contents\\n</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"new contents\\n\")\n }\n ]\n}.\n</code></pre>\n</li>\n</ol>",
|
||||
"inputFields": [
|
||||
{
|
||||
"name": "additions",
|
||||
|
|
|
|||
|
|
@ -1,9 +1,8 @@
|
|||
import GithubSlugger from 'github-slugger'
|
||||
import HtmlEntities from 'html-entities'
|
||||
import { encode } from 'html-entities'
|
||||
import { toString } from 'hast-util-to-string'
|
||||
import { visit } from 'unist-util-visit'
|
||||
const slugger = new GithubSlugger()
|
||||
const entities = new HtmlEntities.XmlEntities()
|
||||
|
||||
const matcher = (node) => node.type === 'element' && ['h2', 'h3', 'h4'].includes(node.tagName)
|
||||
|
||||
|
|
@ -16,7 +15,7 @@ export default function useEnglishHeadings({ englishHeadings }) {
|
|||
// Get the plain text content of the heading node
|
||||
const text = toString(node)
|
||||
// find English heading in the collection
|
||||
const englishHeading = englishHeadings[entities.encode(text)]
|
||||
const englishHeading = englishHeadings[encode(text)]
|
||||
// get English slug
|
||||
const englishSlug = slugger.slug(englishHeading)
|
||||
// use English slug for heading ID and link
|
||||
|
|
|
|||
|
|
@ -1,9 +1,8 @@
|
|||
import liquid from './liquid.js'
|
||||
import cheerio from 'cheerio'
|
||||
import HtmlEntities from 'html-entities'
|
||||
import { encode } from 'html-entities'
|
||||
import stripHtmlComments from 'strip-html-comments'
|
||||
import createProcessor from './create-processor.js'
|
||||
const entities = new HtmlEntities.XmlEntities()
|
||||
|
||||
// used below to remove extra newlines in TOC lists
|
||||
const endLine = '</a>\r?\n'
|
||||
|
|
@ -60,7 +59,7 @@ async function renderContent(template = '', context = {}, options = {}) {
|
|||
return cheerio.load(html, { xmlMode: true })
|
||||
}
|
||||
|
||||
if (options.encodeEntities) html = entities.encode(html)
|
||||
if (options.encodeEntities) html = encode(html)
|
||||
|
||||
return html.trim()
|
||||
} catch (error) {
|
||||
|
|
|
|||
Различия файлов скрыты, потому что одна или несколько строк слишком длинны
|
|
@ -75767,9 +75767,21 @@
|
|||
"type": "boolean",
|
||||
"example": true
|
||||
},
|
||||
"exclude_metadata": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_git_data": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_attachments": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_releases": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_owner_projects": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"repositories": {
|
||||
"type": "array",
|
||||
"items": {
|
||||
|
|
@ -76903,7 +76915,11 @@
|
|||
"guid",
|
||||
"state",
|
||||
"lock_repositories",
|
||||
"exclude_metadata",
|
||||
"exclude_git_data",
|
||||
"exclude_attachments",
|
||||
"exclude_releases",
|
||||
"exclude_owner_projects",
|
||||
"repositories",
|
||||
"url",
|
||||
"created_at",
|
||||
|
|
@ -76940,6 +76956,8 @@
|
|||
"state": "pending",
|
||||
"lock_repositories": true,
|
||||
"exclude_attachments": false,
|
||||
"exclude_releases": false,
|
||||
"exclude_owner_projects": false,
|
||||
"repositories": [
|
||||
{
|
||||
"id": 1296269,
|
||||
|
|
@ -77136,14 +77154,28 @@
|
|||
},
|
||||
"lock_repositories": {
|
||||
"type": "boolean",
|
||||
"example": true,
|
||||
"description": "Indicates whether repositories should be locked (to prevent manipulation) while migrating data.",
|
||||
"default": false
|
||||
},
|
||||
"exclude_attachments": {
|
||||
"type": "boolean",
|
||||
"example": true,
|
||||
"description": "Indicates whether attachments should be excluded from the migration (to reduce migration archive file size).",
|
||||
"default": false
|
||||
},
|
||||
"exclude_releases": {
|
||||
"type": "boolean",
|
||||
"example": true,
|
||||
"description": "Indicates whether releases should be excluded from the migration (to reduce migration archive file size).",
|
||||
"default": false
|
||||
},
|
||||
"exclude_owner_projects": {
|
||||
"type": "boolean",
|
||||
"example": true,
|
||||
"description": "Indicates whether projects owned by the organization or users should be excluded. from the migration.",
|
||||
"default": false
|
||||
},
|
||||
"exclude": {
|
||||
"type": "array",
|
||||
"items": {
|
||||
|
|
@ -77313,9 +77345,21 @@
|
|||
"type": "boolean",
|
||||
"example": true
|
||||
},
|
||||
"exclude_metadata": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_git_data": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_attachments": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_releases": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_owner_projects": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"repositories": {
|
||||
"type": "array",
|
||||
"items": {
|
||||
|
|
@ -78449,7 +78493,11 @@
|
|||
"guid",
|
||||
"state",
|
||||
"lock_repositories",
|
||||
"exclude_metadata",
|
||||
"exclude_git_data",
|
||||
"exclude_attachments",
|
||||
"exclude_releases",
|
||||
"exclude_owner_projects",
|
||||
"repositories",
|
||||
"url",
|
||||
"created_at",
|
||||
|
|
@ -78485,6 +78533,8 @@
|
|||
"state": "pending",
|
||||
"lock_repositories": true,
|
||||
"exclude_attachments": false,
|
||||
"exclude_releases": false,
|
||||
"exclude_owner_projects": false,
|
||||
"repositories": [
|
||||
{
|
||||
"id": 1296269,
|
||||
|
|
@ -78919,9 +78969,21 @@
|
|||
"type": "boolean",
|
||||
"example": true
|
||||
},
|
||||
"exclude_metadata": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_git_data": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_attachments": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_releases": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_owner_projects": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"repositories": {
|
||||
"type": "array",
|
||||
"items": {
|
||||
|
|
@ -80055,7 +80117,11 @@
|
|||
"guid",
|
||||
"state",
|
||||
"lock_repositories",
|
||||
"exclude_metadata",
|
||||
"exclude_git_data",
|
||||
"exclude_attachments",
|
||||
"exclude_releases",
|
||||
"exclude_owner_projects",
|
||||
"repositories",
|
||||
"url",
|
||||
"created_at",
|
||||
|
|
@ -80091,6 +80157,8 @@
|
|||
"state": "exported",
|
||||
"lock_repositories": true,
|
||||
"exclude_attachments": false,
|
||||
"exclude_releases": false,
|
||||
"exclude_owner_projects": false,
|
||||
"repositories": [
|
||||
{
|
||||
"id": 1296269,
|
||||
|
|
@ -378757,9 +378825,21 @@
|
|||
"type": "boolean",
|
||||
"example": true
|
||||
},
|
||||
"exclude_metadata": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_git_data": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_attachments": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_releases": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_owner_projects": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"repositories": {
|
||||
"type": "array",
|
||||
"items": {
|
||||
|
|
@ -379893,7 +379973,11 @@
|
|||
"guid",
|
||||
"state",
|
||||
"lock_repositories",
|
||||
"exclude_metadata",
|
||||
"exclude_git_data",
|
||||
"exclude_attachments",
|
||||
"exclude_releases",
|
||||
"exclude_owner_projects",
|
||||
"repositories",
|
||||
"url",
|
||||
"created_at",
|
||||
|
|
@ -379930,6 +380014,8 @@
|
|||
"state": "pending",
|
||||
"lock_repositories": true,
|
||||
"exclude_attachments": false,
|
||||
"exclude_releases": false,
|
||||
"exclude_owner_projects": false,
|
||||
"repositories": [
|
||||
{
|
||||
"id": 1296269,
|
||||
|
|
@ -380176,6 +380262,18 @@
|
|||
"readOnly": false,
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_releases": {
|
||||
"description": "Do not include releases in the migration",
|
||||
"example": true,
|
||||
"readOnly": false,
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_owner_projects": {
|
||||
"description": "Indicates whether projects owned by the organization or users should be excluded.",
|
||||
"example": true,
|
||||
"readOnly": false,
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude": {
|
||||
"description": "Exclude attributes from the API response to improve performance",
|
||||
"example": [
|
||||
|
|
@ -380355,9 +380453,21 @@
|
|||
"type": "boolean",
|
||||
"example": true
|
||||
},
|
||||
"exclude_metadata": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_git_data": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_attachments": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_releases": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_owner_projects": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"repositories": {
|
||||
"type": "array",
|
||||
"items": {
|
||||
|
|
@ -381491,7 +381601,11 @@
|
|||
"guid",
|
||||
"state",
|
||||
"lock_repositories",
|
||||
"exclude_metadata",
|
||||
"exclude_git_data",
|
||||
"exclude_attachments",
|
||||
"exclude_releases",
|
||||
"exclude_owner_projects",
|
||||
"repositories",
|
||||
"url",
|
||||
"created_at",
|
||||
|
|
@ -381527,6 +381641,8 @@
|
|||
"state": "pending",
|
||||
"lock_repositories": true,
|
||||
"exclude_attachments": false,
|
||||
"exclude_releases": false,
|
||||
"exclude_owner_projects": false,
|
||||
"repositories": [
|
||||
{
|
||||
"id": 1296269,
|
||||
|
|
@ -381977,9 +382093,21 @@
|
|||
"type": "boolean",
|
||||
"example": true
|
||||
},
|
||||
"exclude_metadata": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_git_data": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_attachments": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_releases": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"exclude_owner_projects": {
|
||||
"type": "boolean"
|
||||
},
|
||||
"repositories": {
|
||||
"type": "array",
|
||||
"items": {
|
||||
|
|
@ -383113,7 +383241,11 @@
|
|||
"guid",
|
||||
"state",
|
||||
"lock_repositories",
|
||||
"exclude_metadata",
|
||||
"exclude_git_data",
|
||||
"exclude_attachments",
|
||||
"exclude_releases",
|
||||
"exclude_owner_projects",
|
||||
"repositories",
|
||||
"url",
|
||||
"created_at",
|
||||
|
|
@ -383149,6 +383281,8 @@
|
|||
"state": "exported",
|
||||
"lock_repositories": true,
|
||||
"exclude_attachments": false,
|
||||
"exclude_releases": false,
|
||||
"exclude_owner_projects": false,
|
||||
"repositories": [
|
||||
{
|
||||
"id": 1296269,
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4fa334f28e7ee9a53477d1f0629d8317f325233f2ac1e70a00170c5d91dda311
|
||||
size 506543
|
||||
oid sha256:70e551a2a5a9cc622eed0e1d96a1088bae6342f970427a7ba56f4aee53b74a52
|
||||
size 506849
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:7021451093e727c584210a5ad2b1c7f85659fe3613ce86694ad34351ffd28af7
|
||||
size 802598
|
||||
oid sha256:264588cc7e0b43656c770702a9e6260e2b4bbfeff6e43b4d5922dfb04a64a687
|
||||
size 802685
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:16cb8f8335b8e726be7fb007af1492bcdd395b870faa845c57b1d0cbf4e1559c
|
||||
size 469555
|
||||
oid sha256:f3d3d3c6f024ce4b67b6046aca13b83a75adba476c43c5d92853beedfdf3203a
|
||||
size 469562
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:bb5dcfca479f9cfbb0cbc540768075659530aecd18c9c2622ec3f423b9dea5d0
|
||||
size 2077823
|
||||
oid sha256:97023fa03dd6d13d644c9ce8fe723ac20770eaf171f6cf778ff87d2d2fdad280
|
||||
size 2077605
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e787b9f98a7606be25739f9dec2deede9435799e1e7a8b9e5da41a567145359a
|
||||
size 430209
|
||||
oid sha256:a9061864fa8f40a716240bde02ef0f8ff867ed97fc74350818df2f3d52493a42
|
||||
size 429974
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:fefc98577b850ebf1e3d805b39e62d002c79870819f411ada68d00bb39d3a9d7
|
||||
size 1680984
|
||||
oid sha256:f1207df0db78559e2cbd3e80e241128339a4da60b9e9282d491125c66f16c979
|
||||
size 1680673
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:aadc2d4130093141de485fa1b93260fe9a8e3b106aec3e1f10fd0710212e791f
|
||||
size 280499
|
||||
oid sha256:81160ab07a657bb0a24a4d2e70bf70b614fb5be81e0d9e5ffdf3f6b3556cc86b
|
||||
size 280186
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:bf9899a32ee9bd44d18f23926110eddf850a0d6820352c9d7ee0866663d1277e
|
||||
size 1068689
|
||||
oid sha256:f43ebf6fd0252ab57dffcf0ea97b9f645fa791acefdd895a5aa1c2bb2162814b
|
||||
size 1067629
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:3b9eafdaae47159e1404737bb0d40c59383a98683f15c06baa60d674ab94e604
|
||||
size 528997
|
||||
oid sha256:92123fae547e8bdb14c22d411d7372dba8db4524749826f963123cab844ac1d6
|
||||
size 528804
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:b0f3dc594d1c854d8bffe9944e7f6c1a0f2e5f7b42408a6a2dc09cee56a08ee2
|
||||
size 2798123
|
||||
oid sha256:f1022edac40d840e8dc4190231dd06c3e207bad9e6f5dffd91c73ef97994b100
|
||||
size 2797116
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:f71ad7a623aab1bc8123fb785b1521cf172efd096d9960dbeb799f459351cc98
|
||||
size 443745
|
||||
oid sha256:27c699c2216d0ed238ec8ba774a2662d19e4867ad3e6a4878ab0ddedaa8a62ee
|
||||
size 443802
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9788a05c24cfa4b069b91efee0536707194247d921418d240debb89764a31c58
|
||||
size 1853502
|
||||
oid sha256:c878f74c6b9b46c3b8ae80063ce934b087884b375dae00ab162b0c04c13300b5
|
||||
size 1853379
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:0a7575b58722828cca818f40716b8c9106d01aee783d6f4e12a6bc89609c5a7c
|
||||
size 524743
|
||||
oid sha256:c60e9cc78a86e0aaaba86931b9c77846ddeda7ba08322c33b504e9e86a330b99
|
||||
size 524728
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:75570be80a894ccfd016a53d4c0494f31c9af1c70df8abb04f52c6019d4c2ff3
|
||||
size 833930
|
||||
oid sha256:de1018d3d2450ef1a8a2dcae510d9557b6db9097d33bd59ac7412ba7503baf35
|
||||
size 833600
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c1a25734691355771f4e95169fc4fec8e3685418ba2fe41a7737063656ff65fe
|
||||
size 490374
|
||||
oid sha256:30ad95965eed0e972cdc3e94c3f186a715822f8cbfa73eeffe31cfe7ac05c8d3
|
||||
size 490536
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e652a928580fb1795c27d642b9e919a12f089e190fd16f41fdba5300797bef69
|
||||
size 2178831
|
||||
oid sha256:375a9331337828e628f169fbe1c7722d172c4b0cfd7484c03a1b5f1a45d2ad70
|
||||
size 2180492
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2e13d6ae3426fc34450d0c63ca4c910d7a5b8cc88976ede07e195e38f0238f21
|
||||
size 450721
|
||||
oid sha256:36c176b1c80a439b0428dc0988ab123a5bdee290328ee069634e55b213bff25d
|
||||
size 449541
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:258086c4aab65d8ed70da3b38a1f78eaa1403e41063f3e61459cc6b5add108e8
|
||||
size 1754597
|
||||
oid sha256:51043302da4ce62c3916045fb69ca0ec7543654dbe0be107f6252ded878d37b8
|
||||
size 1754146
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:f16b3fedcd1ba0d06f9a0bd921ce68ddc37c0221332bd83b10ec2ee8c8bb79c2
|
||||
size 277949
|
||||
oid sha256:c1fe6356482d63ed27da20c6c59eb0179b6a2a9dbaa2d88d5aacf822712c33b6
|
||||
size 277925
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:263237f7db3a0b519b42ec9606c4fce0e7a713fe174707eea4bfc3a555fafd96
|
||||
size 1056002
|
||||
oid sha256:53453b84084600b108bc1f3af056da786b081e4e9b3df7524fecbfa216686601
|
||||
size 1056025
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:e32e993848127b896386b9582fb7423adab3361d4f9eccb9594c63133e63559e
|
||||
size 550599
|
||||
oid sha256:2c1d2fa9e4b0be2d0591189e907f284d84365d2b758fac55bf935e4f93637214
|
||||
size 550576
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:1e7a30aaf067305cf2ec7234492d453490bd4fb7d7a6ea9eb7bb446c7a6529fd
|
||||
size 2913349
|
||||
oid sha256:42c5d79da8c575aa123e22d3ffff3a2a60e96e0cdec126a696e1739a819bc965
|
||||
size 2913024
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:50a97cbb7b97725f09e23a3c17d04bab79cdaf408609a12ea680f6ffa7004c50
|
||||
size 464864
|
||||
oid sha256:272436b4231dbcb1533b418ee0db755c1ecc6512913e6a9b88544325942ff486
|
||||
size 464693
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:799d828c7be83733f176c04b0b73bc98f703cbd3c1053ee13ad93c27ee555155
|
||||
size 1936522
|
||||
oid sha256:919d6f1527c1d2366a5814d74f712d5bc4feaac5ae3c163e1781bdfe13cbbecb
|
||||
size 1937103
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:69ba84ba9bf80573a4f6cb3239b3863ffba2b26d2841987dfe23875e9f6cccc0
|
||||
size 534111
|
||||
oid sha256:4f7561624856a67817727ae365ab7bd1496c43aa2a761b9f8e473ab354798874
|
||||
size 534066
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:8e7bfda93dae577acfb08c0315419f975887cf58b0418f43226faf84094d890f
|
||||
size 846239
|
||||
oid sha256:ec39574be7e165335f1baa8c9f86b7b487dc9ba734557ec1d5ca959cb42dd10a
|
||||
size 846118
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9e31638ef6cc8583cbc7f2d913d6873277c6d73069ed5ad64f98f7ab57bc616f
|
||||
size 497752
|
||||
oid sha256:42af86d28bf52bf30b3e0d554b1f0d2295ce90bd738f4fefa70e7494bb1b706b
|
||||
size 497160
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:a6dfc2b26e282863c985d98af39d875a25732e1e95a6c9d60970de3e108b7deb
|
||||
size 2222712
|
||||
oid sha256:b1478d7ca946dffc640ff4e9e57fcff80aaf1b50ec1c1e6345cf92d380c1ed93
|
||||
size 2220838
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:95c311a5fabb0942223f8b0a117ca9e411a7e196c1dcf01e20bcf040b053bd3b
|
||||
size 459008
|
||||
oid sha256:789303eba793051bb00dd7dcc6712e1a4baadf3d6c3b43902f9582860c8d0a96
|
||||
size 459047
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:ecbe67f5705a86ffb08529a8f18dec0a684b66f162e5bac5074bb195686f03fb
|
||||
size 1790770
|
||||
oid sha256:1e627f9de4833d6d175ce97f19f6afa62dfbad14fbd44c834a955bbd962ab849
|
||||
size 1790038
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:38eb1055e3cfe291b30ee4fa0ca2cae8dbae603a022b4c379816b1e70e462857
|
||||
size 278594
|
||||
oid sha256:fbd66c664d78d6d320804bf3ac12a4b5d133e49b3e56227863d4b39abacb4bef
|
||||
size 278463
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:6dc905946d0107fb03629cc8e661f892215efa2ac49bcb05f8d852afcc94939c
|
||||
size 1057492
|
||||
oid sha256:643bd38a221456d8fa8ddaca83685bbad8d4e4f301660a19fbb5c0ab8a2d66c6
|
||||
size 1056355
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:15dd36ae42a1d562ecafd15149fb5082bb66e5e6c37fcd5b04807fab16299ce6
|
||||
size 558897
|
||||
oid sha256:d32fd4ac74cca1cd48822204d269804259c057fb62ffcd634fad50ef4306bba9
|
||||
size 558699
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:10df72436e3eb217d39b627610924b727e2a62865dca405d73e95e1f06cac0d6
|
||||
size 2965004
|
||||
oid sha256:3f869360df6f4881b2b6c0482b93cbf8dae6267b3a3004f081bf288c975c9615
|
||||
size 2964919
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:1b60e4437127dfbe1b3d61e5733a3f9d0da51b7d5fc65bee4813c0acbe8b8e60
|
||||
size 472565
|
||||
oid sha256:ce247474b9a38700142d67f5b79f67a32e3faf7eb9c72bfb7189e2a74cd0f11e
|
||||
size 472242
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:33935e761f7b5f636e761e6cb80cdd771e75d9e277db82b994a57aa779567087
|
||||
size 1973862
|
||||
oid sha256:c394f776be450af39853724de87c788872f05da421ee5c1dcae0c85582c668a3
|
||||
size 1971999
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:752d1e6bed6496f15b45d294b9c65e39d38d3012fc31c7b2e5053696034e90ac
|
||||
size 539718
|
||||
oid sha256:205849e5bc4ed3e6e889bd8cf820fb0502072b0c83e049eef3b8ccc7579ca7de
|
||||
size 539854
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:eba6f931829115a65b70a6076048c825c01a2e3120563f79ea37acf831d52dba
|
||||
size 853670
|
||||
oid sha256:d62e8ab3d734332ae4871cd644e1abd437c7ef9de8416aadc84a3dc166239ce4
|
||||
size 853477
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:acd9baec9f1994300a6f6576bc946601ee70e64abbdc224d8fbecd6b486b26e0
|
||||
size 501691
|
||||
oid sha256:89c1813cce362879adcbd363a425f152aef03f151395a6a987c1c013a1f617e2
|
||||
size 501988
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:c253f418de9462efe448348d8598d9d1a1015886af43248304a01ac0817b4573
|
||||
size 2244789
|
||||
oid sha256:576700f73ae7d4d51f67517cb639b0d49ae3dca60311f6ed2f9648131d7ccadc
|
||||
size 2246352
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2707661dd6ad439ac66081142cb9e50cd3a0f6357f202942847a6f57bdb5473b
|
||||
size 467647
|
||||
oid sha256:d9e4ff11995f9951108663de09e6d742c64d27ac5abf2969cec55e5255803db3
|
||||
size 466424
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9dfdc33297fc687a660b26c96ef7a87fb6fa7a0a280205bf99c0a82ef831d64f
|
||||
size 1822981
|
||||
oid sha256:c4048579634c575256fd84e7c16bfeebc33acb4832b2ea832de55df4d14a8eb3
|
||||
size 1822877
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:afc462eb79ff08ab6006b9168eee86193ddb2b549774676d05dc90ca9e61dcc1
|
||||
size 278725
|
||||
oid sha256:863a98bd35a28cdb9186524cec999a5b04f62ab57dd8dea9c4f469af46c35a5b
|
||||
size 278407
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9b40194035eba413f8be7618d1d65e5bd6442aec08fda5bc1d51a0c0652029da
|
||||
size 1058438
|
||||
oid sha256:670036408a01c058f8a5ec74fe44650207e31c2cf9fa5d867d4e6536a9ce4d89
|
||||
size 1057070
|
||||
|
|
|
|||
|
|
@ -1,3 +1,3 @@
|
|||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:7c38ee33ab3d40517af5e3820415845e3ad5a94114b58de34269b33980006765
|
||||
size 564883
|
||||
oid sha256:18228bbb8db97ad4cc1d1d62a9eb0be882cfb909c46d3cdd36e89561c47c1ecc
|
||||
size 564747
|
||||
|
|
|
|||
Некоторые файлы не были показаны из-за слишком большого количества измененных файлов Показать больше
Загрузка…
Ссылка в новой задаче