Merge branch 'main' into patch-2
This commit is contained in:
mc
BIN
assets/images/help/releases/delete-release-trash.png
Normal file
BIN
assets/images/help/releases/delete-release-trash.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 34 KiB |
BIN
assets/images/help/releases/draft-release-button-with-search.png
Normal file
BIN
assets/images/help/releases/draft-release-button-with-search.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 7.1 KiB |
BIN
assets/images/help/releases/edit-release-pencil.png
Normal file
BIN
assets/images/help/releases/edit-release-pencil.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 34 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 35 KiB |
BIN
assets/images/help/releases/refreshed-compare-tags.png
Normal file
BIN
assets/images/help/releases/refreshed-compare-tags.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 27 KiB |
BIN
assets/images/help/releases/refreshed-release-latest.png
Normal file
BIN
assets/images/help/releases/refreshed-release-latest.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 21 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 125 KiB |
BIN
assets/images/help/releases/release-compare-button.png
Normal file
BIN
assets/images/help/releases/release-compare-button.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 21 KiB |
BIN
assets/images/help/releases/release-compare-menu.png
Normal file
BIN
assets/images/help/releases/release-compare-menu.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 16 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 57 KiB After Width: | Height: | Size: 35 KiB |
BIN
assets/images/help/releases/release-title-old.png
Normal file
BIN
assets/images/help/releases/release-title-old.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 18 KiB |
BIN
assets/images/help/releases/release-title.png
Normal file
BIN
assets/images/help/releases/release-title.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 15 KiB |
BIN
assets/images/help/releases/search-releases.png
Normal file
BIN
assets/images/help/releases/search-releases.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 5.9 KiB |
@@ -25,7 +25,11 @@ topics:
|
||||
|
||||
## Creating a workflow template
|
||||
|
||||
Workflow templates can be created by users with write access to the organization's `.github` repository. The templates can then be used by organization members who have permission to create workflows. You can share workflow templates if your organization's repository is public or if the repository is private and on an Enterprise plan.
|
||||
Workflow templates can be created by users with write access to the organization's `.github` repository. The templates can then be used by organization members who have permission to create workflows.
|
||||
|
||||
{% ifversion fpt %}
|
||||
Your workflow templates can be used to create workflows in public repositories only. Organizations using {% data variables.product.prodname_ghe_cloud %} can also use workflow templates to create workflows in private repositories. For more information, see the [{% data variables.product.prodname_ghe_cloud %} documentation](/enterprise-cloud@latest/actions/learn-github-actions/creating-workflow-templates).
|
||||
{% endif %}
|
||||
|
||||
{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
|
||||
{% note %}
|
||||
|
||||
@@ -20,7 +20,7 @@ shortTitle: Add a status badge
|
||||
You reference the workflow by the name of your workflow file.
|
||||
|
||||
```markdown
|
||||
|
||||
|
||||
```
|
||||
## Using the workflow file name
|
||||
|
||||
|
||||
@@ -624,6 +624,31 @@ A `top`-like interface for current Git operations.
|
||||
ghe-btop [ <port number> | --help | --usage ]
|
||||
```
|
||||
|
||||
#### ghe-governor
|
||||
|
||||
This utility helps to analyze Git traffic. It queries _Governor_ data files, located under `/data/user/gitmon`. {% data variables.product.company_short %} holds one hour of data per file, retained for two weeks. For more information, see [Analyzing Git traffic using Governor](https://github.community/t/analyzing-git-traffic-using-governor/13516) in {% data variables.product.prodname_gcf %}.
|
||||
|
||||
```bash
|
||||
ghe-governor <subcommand> <column> [options]
|
||||
```
|
||||
|
||||
```
|
||||
ghe-governor -h
|
||||
Usage: ghe-governor [-h] <subcommand> args
|
||||
|
||||
OPTIONS:
|
||||
-h | --help Show this message.
|
||||
|
||||
Valid subcommands are:
|
||||
aggregate Find the top (n) groups of queries for a grouping function and metric
|
||||
health Summarize all recent activity on one or more servers
|
||||
top Find the top (n) queries for a given metric
|
||||
dump Dump individual operations
|
||||
test-quotas Check quota information
|
||||
|
||||
Try ghe-governor <subcommand> --help for more information on the arguments each subcommand takes.
|
||||
```
|
||||
|
||||
### ghe-repo
|
||||
|
||||
This utility allows you to change to a repository's directory and open an interactive shell as the `git` user. You can perform manual inspection or maintenance of a repository via commands like `git-*` or `git-nw-*`.
|
||||
|
||||
@@ -21,6 +21,7 @@ redirect_from:
|
||||
- /github/articles/verifying-your-enterprise-accounts-domain
|
||||
- /early-access/github/articles/verifying-your-enterprise-accounts-domain
|
||||
- /github/setting-up-and-managing-your-enterprise/verifying-or-approving-a-domain-for-your-enterprise-account
|
||||
- /admin/policies/verifying-or-approving-a-domain-for-your-enterprise
|
||||
---
|
||||
|
||||
## About verification of domains
|
||||
|
||||
@@ -24,7 +24,14 @@ The time required to failover depends on how long it takes to manually promote t
|
||||
```shell
|
||||
$ ghe-maintenance -s
|
||||
```
|
||||
2. When the number of active Git operations reaches zero, wait 30 seconds.
|
||||
2. When the number of active Git operations, MySQL queries, and Resque jobs reaches zero, wait 30 seconds.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** Nomad will always have jobs running, even in maintenance mode, so you can safely ignore these jobs.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
3. To verify all replication channels report `OK`, use the `ghe-repl-status -vv` command.
|
||||
```shell
|
||||
$ ghe-repl-status -vv
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: About upgrades to new releases
|
||||
shortTitle: About upgrades
|
||||
intro: '{% ifversion ghae %}Your {% data variables.product.product_name %} enterprise is updated with the latest features and bug fixes on a regular basis by {% data variables.product.company_short %}.{% else %}You can benefit from new features and bug fixes for {% data variables.product.product_name %} by upgrading your enterprise to a newly released version.{% endif %}'
|
||||
intro: '{% ifversion ghae %}Your enterprise on {% data variables.product.product_name %} is updated with the latest features and bug fixes on a regular basis by {% data variables.product.company_short %}.{% else %}You can benefit from new features and bug fixes for {% data variables.product.product_name %} by upgrading your enterprise to a newly released version.{% endif %}'
|
||||
versions:
|
||||
ghes: '>=3.0'
|
||||
ghae: '*'
|
||||
@@ -11,13 +11,13 @@ topics:
|
||||
- Upgrades
|
||||
---
|
||||
|
||||
{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through major and minor releases. {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} is a fully managed service, so {% data variables.product.company_short %} completes the upgrade process for your enterprise.{% endif %}
|
||||
{% data variables.product.product_name %} is constantly improving, with new functionality and bug fixes introduced through feature and patch releases. {% ifversion ghae %}{% data variables.product.prodname_ghe_managed %} is a fully managed service, so {% data variables.product.company_short %} completes the upgrade process for your enterprise.{% endif %}
|
||||
|
||||
Major releases include new functionality and feature upgrades and typically occur quarterly. {% ifversion ghae %}{% data variables.product.company_short %} will upgrade your enterprise to the latest major release. You will be given advance notice of any planned downtime for your enterprise.{% endif %}
|
||||
Feature releases include new functionality and feature upgrades and typically occur quarterly. {% ifversion ghae %}{% data variables.product.company_short %} will upgrade your enterprise to the latest feature release. You will be given advance notice of any planned downtime for your enterprise.{% endif %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
Starting with {% data variables.product.prodname_ghe_server %} 3.0, all major releases begin with at least one release candidate. Release candidates are proposed major releases, with a complete feature set. There may be bugs or issues in a release candidate which can only be found through feedback from customers actually using {% data variables.product.product_name %}.
|
||||
Starting with {% data variables.product.prodname_ghe_server %} 3.0, all feature releases begin with at least one release candidate. Release candidates are proposed feature releases, with a complete feature set. There may be bugs or issues in a release candidate which can only be found through feedback from customers actually using {% data variables.product.product_name %}.
|
||||
|
||||
You can get early access to the latest features by testing a release candidate as soon as the release candidate is available. You can upgrade to a release candidate from a supported version and can upgrade from the release candidate to later versions when released. You should upgrade any environment running a release candidate as soon as the release is generally available. For more information, see "[Upgrade requirements](/admin/enterprise-management/upgrade-requirements)."
|
||||
|
||||
@@ -29,13 +29,13 @@ We'll use your feedback to apply bug fixes and any other necessary changes to cr
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning**: The upgrade to a new major release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. You can inform your users about downtime by publishing a global announcement banner, using your enterprise settings or the REST API. For more information, see "[Customizing user messages on your instance](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" and "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)."
|
||||
**Warning**: The upgrade to a new feature release will cause a few hours of downtime, during which none of your users will be able to use the enterprise. You can inform your users about downtime by publishing a global announcement banner, using your enterprise settings or the REST API. For more information, see "[Customizing user messages on your instance](/admin/user-management/customizing-user-messages-on-your-instance#creating-a-global-announcement-banner)" and "[{% data variables.product.prodname_enterprise %} administration](/rest/reference/enterprise-admin#announcements)."
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
{% ifversion ghes %}
|
||||
|
||||
Minor releases, which consist of hot patches and bug fixes only, happen more frequently. Minor releases are generally available when first released, with no release candidates. Upgrading to a minor release typically requires less than five minutes of downtime.
|
||||
Patch releases, which consist of hot patches and bug fixes only, happen more frequently. Patch releases are generally available when first released, with no release candidates. Upgrading to a patch release typically requires less than five minutes of downtime.
|
||||
|
||||
To upgrade your enterprise to a new release, see "[Release notes](/enterprise-server/admin/release-notes)" and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)."
|
||||
|
||||
|
||||
@@ -21,6 +21,8 @@ topics:
|
||||
|
||||
The root filesystem is included in the distributed machine image. It contains the base operating system and the {% data variables.product.prodname_ghe_server %} application environment. The root filesystem should be treated as ephemeral. Any data on the root filesystem will be replaced when upgrading to future {% data variables.product.prodname_ghe_server %} releases.
|
||||
|
||||
The root storage volume is split into two equally-sized partitions. One of the partitions will be mounted as the root filesystem (`/`). The other partition is only mounted during upgrades and rollbacks of upgrades as `/mnt/upgrade`, to facilitate easier rollbacks if necessary. For example, if a 200GB root volume is allocated, there will be 100GB allocated to the root filesystem and 100GB reserved for the upgrades and rollbacks.
|
||||
|
||||
The root filesystem contains:
|
||||
- Custom certificate authority (CA) certificates (in */usr/local/share/ca-certificates*)
|
||||
- Custom networking configurations
|
||||
|
||||
@@ -4,6 +4,7 @@ intro: 'You can set policies in {% data variables.product.product_name %} to red
|
||||
redirect_from:
|
||||
- /enterprise/admin/developer-workflow
|
||||
- /enterprise/admin/policies
|
||||
- /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account
|
||||
versions:
|
||||
ghec: '*'
|
||||
ghes: '*'
|
||||
|
||||
@@ -44,7 +44,7 @@ If your enterprise uses {% data variables.product.prodname_emus %}, enterprise o
|
||||
|
||||
## {% ifversion ghec %}Inviting{% elsif ghes %}Adding{% endif %} an enterprise administrator to your enterprise account
|
||||
|
||||
{% ifversion ghec %}After you invite someone to join the enterprise account, they must accept the emailed invitation before they can access the enterprise account.{% endif %}
|
||||
{% ifversion ghec %}After you invite someone to join the enterprise account, they must accept the emailed invitation before they can access the enterprise account. Pending invitations will expire after 7 days.{% endif %}
|
||||
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.people-tab %}
|
||||
|
||||
@@ -22,7 +22,9 @@ shortTitle: Import to your enterprise
|
||||
---
|
||||
## Applying the imported data on {% data variables.product.prodname_ghe_server %}
|
||||
|
||||
Once you have [prepared your migration](/admin/user-management/preparing-to-migrate-data-to-your-enterprise) you can use the following steps to complete the migration.
|
||||
Before you can migrate data to your enterprise, you must prepare the data and resolve any conflicts. For more information, see "[Preparing to migrate data to your enterprise](/admin/user-management/preparing-to-migrate-data-to-your-enterprise)."
|
||||
|
||||
After you prepare the data and resolve conflicts, you can apply the imported data on {% data variables.product.product_name %}.
|
||||
|
||||
{% data reusables.enterprise_installation.ssh-into-target-instance %}
|
||||
|
||||
|
||||
@@ -25,7 +25,7 @@ To maintain account security, you can regularly review your SSH keys list and re
|
||||
If you haven't used your SSH key for a year, then {% data variables.product.prodname_dotcom %} will automatically delete your inactive SSH key as a security precaution. For more information, see "[Deleted or missing SSH keys](/articles/deleted-or-missing-ssh-keys)."
|
||||
{% endif %}
|
||||
|
||||
If you're a member of an organization that provides SSH certificates, you can use your certificate to access that organization's repositories without adding the certificate to your account on {% data variables.product.product_location %}. For more information, see "[About SSH certificate authorities](/articles/about-ssh-certificate-authorities)."
|
||||
If you're a member of an organization that provides SSH certificates, you can use your certificate to access that organization's repositories without adding the certificate to your account on {% data variables.product.product_name %}. You cannot use your certificate to access forks of the organization's repositories that are owned by your user account. For more information, see "[About SSH certificate authorities](/articles/about-ssh-certificate-authorities)."
|
||||
|
||||
## Further reading
|
||||
|
||||
|
||||
@@ -18,6 +18,12 @@ After you purchase or upgrade a license for {% data variables.product.prodname_e
|
||||
|
||||
## Uploading your license to {% data variables.product.product_location_enterprise %}
|
||||
|
||||
{% warning %}
|
||||
|
||||
**Warning:** Updating your license causes a small amount of downtime for {% data variables.product.product_location %}.
|
||||
|
||||
{% endwarning %}
|
||||
|
||||
1. Sign into {% data variables.product.product_location_enterprise %} as a site administrator.
|
||||
{% data reusables.enterprise-accounts.access-enterprise %}
|
||||
{% data reusables.enterprise-accounts.settings-tab %}
|
||||
|
||||
@@ -47,17 +47,20 @@ Below is a list of some of the available keyboard shortcuts.
|
||||
|<kbd>.</kbd>| Opens a repository or pull request in the web-based editor. For more information, see "[Web-based editor](/codespaces/developing-in-codespaces/web-based-editor)."{% endif %}
|
||||
| <kbd>control b</kbd> or <kbd>command b</kbd> | Inserts Markdown formatting for bolding text
|
||||
| <kbd>control i</kbd> or <kbd>command i</kbd> | Inserts Markdown formatting for italicizing text
|
||||
| <kbd>control k</kbd> or <kbd>command k</kbd> | Inserts Markdown formatting for creating a link
|
||||
| <kbd>control k</kbd> or <kbd>command k</kbd> | Inserts Markdown formatting for creating a link{% ifversion fpt or ghec or ghae-next or ghes > 3.3 %}
|
||||
| <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd> | Inserts Markdown formatting for an ordered list
|
||||
| <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd> | Inserts Markdown formatting for an unordered list
|
||||
| <kbd>control shift .</kbd> or <kbd>command shift.</kbd> | Inserts Markdown formatting for a quote{% endif %}
|
||||
|<kbd>e</kbd> | Open source code file in the **Edit file** tab
|
||||
|<kbd>control f</kbd> or <kbd>command f</kbd> | Start searching in file editor
|
||||
|<kbd>control g</kbd> or <kbd>command g</kbd> | Find next
|
||||
|<kbd>shift control g</kbd> or <kbd>shift command g</kbd> | Find previous
|
||||
|<kbd>shift control f</kbd> or <kbd>command option f</kbd> | Replace
|
||||
|<kbd>shift control r</kbd> or <kbd>shift command option f</kbd> | Replace all
|
||||
|<kbd>control shift g</kbd> or <kbd>command shift g</kbd> | Find previous
|
||||
|<kbd>control shift f</kbd> or <kbd>command option f</kbd> | Replace
|
||||
|<kbd>control shift r</kbd> or <kbd>command shift option f</kbd> | Replace all
|
||||
|<kbd>alt g</kbd> | Jump to line
|
||||
|<kbd>control z</kbd> or <kbd>command z</kbd> | Undo
|
||||
|<kbd>control y</kbd> or <kbd>command y</kbd> | Redo
|
||||
|<kbd>cmd + shift + p</kbd> | Toggles between the **Edit file** and **Preview changes** tabs
|
||||
|<kbd>command shift p</kbd> | Toggles between the **Edit file** and **Preview changes** tabs
|
||||
|<kbd>control s</kbd> or <kbd>command s</kbd> | Write a commit message
|
||||
|
||||
For more keyboard shortcuts, see the [CodeMirror documentation](https://codemirror.net/doc/manual.html#commands).
|
||||
|
||||
@@ -148,5 +148,5 @@ To delete a view:
|
||||
|
||||
## Further reading
|
||||
|
||||
- "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)
|
||||
- "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project)
|
||||
- "[About projects (beta)](/issues/trying-out-the-new-projects-experience/about-projects)"
|
||||
- "[Creating a project (beta)](/issues/trying-out-the-new-projects-experience/creating-a-project)"
|
||||
|
||||
@@ -22,6 +22,8 @@ After you add an SSH CA to your organization or enterprise account, you can use
|
||||
|
||||
For example, you can build an internal system that issues a new certificate to your developers every morning. Each developer can use their daily certificate to work on your organization's repositories on {% data variables.product.product_name %}. At the end of the day, the certificate can automatically expire, protecting your repositories if the certificate is later compromised.
|
||||
|
||||
Members will not be able to use their certificates to access forks of your repositories that are owned by their user accounts.
|
||||
|
||||
When you issue each certificate, you must include an extension that specifies which {% data variables.product.product_name %} user the certificate is for. For example, you can use OpenSSH's `ssh-keygen` command, replacing _KEY-IDENTITY_ with your key identity and _USERNAME_ with a {% data variables.product.product_name %} username. The certificate you generate will be authorized to act on behalf of that user for any of your organization's resources. Make sure you validate the user's identity before you issue the certificate.
|
||||
|
||||
```shell
|
||||
|
||||
@@ -14,10 +14,16 @@ topics:
|
||||
shortTitle: Create accounts for people
|
||||
---
|
||||
|
||||
Because you access an organization by logging in to a personal account, each of your team members needs a personal account. Once you have user names for each person you'd like to add to your organization, you can add them to teams.
|
||||
## About user accounts
|
||||
|
||||
Because you access an organization by logging in to a user account, each of your team members needs to create their own user account. After you have usernames for each person you'd like to add to your organization, you can add the users to teams.
|
||||
|
||||
{% ifversion fpt or ghec %}
|
||||
If you need greater control over the user accounts of your organization members, consider {% data variables.product.prodname_emus %}. {% data reusables.enterprise-accounts.emu-short-summary %}
|
||||
{% endif %}
|
||||
|
||||
## Adding users to your organization
|
||||
|
||||
1. Provide each person instructions to [create a personal account](/articles/signing-up-for-a-new-github-account).
|
||||
1. Provide each person instructions to [create a user account](/articles/signing-up-for-a-new-github-account).
|
||||
2. Ask for the username of each person you want to give organization membership to.
|
||||
3. [Invite the new personal accounts to join](/articles/inviting-users-to-join-your-organization) your organization. Use [organization roles](/articles/permission-levels-for-an-organization) and [repository permissions](/articles/repository-permission-levels-for-an-organization) to limit the access of each account.
|
||||
|
||||
@@ -65,7 +65,7 @@ If your instance has subdomain isolation enabled:
|
||||
</repository>
|
||||
<repository>
|
||||
<id>github</id>
|
||||
<url>https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/*</url>
|
||||
<url>https://{% ifversion fpt or ghec %}maven.pkg.github.com{% else %}maven.HOSTNAME{% endif %}/OWNER/REPOSITORY</url>
|
||||
<snapshots>
|
||||
<enabled>true</enabled>
|
||||
</snapshots>
|
||||
@@ -107,7 +107,7 @@ If your instance has subdomain isolation disabled:
|
||||
</repository>
|
||||
<repository>
|
||||
<id>github</id>
|
||||
<url>HOSTNAME/_registry/maven/OWNER/*</url>
|
||||
<url>HOSTNAME/_registry/maven/OWNER/REPOSITORY</url>
|
||||
<snapshots>
|
||||
<enabled>true</enabled>
|
||||
</snapshots>
|
||||
|
||||
@@ -71,7 +71,15 @@ People with admin permissions for a repository can change an existing repository
|
||||
|
||||
{% data reusables.repositories.about-internal-repos %} For more information on innersource, see {% data variables.product.prodname_dotcom %}'s whitepaper "[An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/)."
|
||||
|
||||
People who are members of an organization within the enterprise have read permissions to internal repositories, but internal repositories are not visible to people {% ifversion fpt or ghec %}outside of the enterprise{% else %}who are not members of an organization{% endif %}, including outside collaborators on organization repositories. For more information, see {% ifversion fpt or ghae or ghec %}"[Roles in an enterprise](/admin/user-management/managing-users-in-your-enterprise/roles-in-an-enterprise#enterprise-members)" and {% endif %}"[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)."
|
||||
All enterprise members have read permissions to the internal repository, but internal repositories are not visible to people {% ifversion fpt or ghec %}outside of the enterprise{% else %}who are not members of any organization{% endif %}, including outside collaborators on organization repositories. For more information, see "[Roles in an enterprise](/github/setting-up-and-managing-your-enterprise/roles-in-an-enterprise#enterprise-members)" and "[Repository permission levels for an organization](/articles/repository-permission-levels-for-an-organization)."
|
||||
|
||||
{% ifversion ghes %}
|
||||
{% note %}
|
||||
|
||||
**Note:** A user must be part of an organization to be an enterprise member and have access to internal repositories. If a user on {% data variables.product.product_location %} is not a member of any organization, that user will not have access to internal repositories.
|
||||
|
||||
{% endnote %}
|
||||
{% endif %}
|
||||
|
||||
{% data reusables.repositories.internal-repo-default %}
|
||||
|
||||
|
||||
@@ -26,8 +26,8 @@ topics:
|
||||
|
||||
When you transfer a repository to a new owner, they can immediately administer the repository's contents, issues, pull requests, releases, project boards, and settings.
|
||||
|
||||
Prerequisites for repository transfers: {% ifversion fpt or ghec %}
|
||||
- When you transfer a repository that you own to another user account, the new owner will receive a confirmation email. The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %}
|
||||
Prerequisites for repository transfers:
|
||||
- When you transfer a repository that you own to another user account, the new owner will receive a confirmation email.{% ifversion fpt or ghec %} The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.{% endif %}
|
||||
- To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization.
|
||||
- The target account must not have a repository with the same name, or a fork in the same network.
|
||||
- The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.
|
||||
|
||||
@@ -19,7 +19,9 @@ topics:
|
||||
---
|
||||
## About releases
|
||||
|
||||
{% ifversion fpt or ghes > 3.2 or ghae-issue-4972 or ghec %}
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
|
||||
|
||||
{% elsif ghes > 3.2 or ghae-issue-4972 %}
|
||||
|
||||
{% else %}
|
||||
|
||||
|
||||
@@ -13,12 +13,6 @@ communityRedirect:
|
||||
href: 'https://github.com/github/feedback/discussions/categories/releases-feedback'
|
||||
---
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** {% data reusables.repositories.auto-gen-release-public-beta %}
|
||||
|
||||
{% endnote %}
|
||||
|
||||
## About automatically generated release notes
|
||||
|
||||
Automatically generated release notes provide an automated alternative to manually writing release notes for your {% data variables.product.prodname_dotcom %} releases. With automatically generated release notes, you can quickly generate an overview of the contents of a release. You can also customize your automated release notes, using labels to create custom categories to organize pull requests you want to include, and exclude certain labels and users from appearing in the output.
|
||||
|
||||
@@ -16,6 +16,14 @@ redirect_from:
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.releases %}
|
||||
3. Next to the release you want to use as your base, click **Compare**.
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
4. Use the "Compare" drop-down menu and select the tags you want to compare.
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
@@ -16,6 +16,7 @@ children:
|
||||
- /about-releases
|
||||
- /managing-releases-in-a-repository
|
||||
- /viewing-your-repositorys-releases-and-tags
|
||||
- /searching-a-repositorys-releases
|
||||
- /linking-to-releases
|
||||
- /comparing-releases
|
||||
- /automatically-generated-release-notes
|
||||
|
||||
@@ -15,9 +15,16 @@ topics:
|
||||
---
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.releases %}
|
||||
3. Find the release you want to link to and click the version number.
|
||||
|
||||
3. Alternatively, right click **Latest Release** and copy the URL to share it. The suffix of this URL is always `/releases/latest`.
|
||||
3. To copy a unique URL to your clipboard, find the release you want to link to, right click the title, and copy the URL.
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
1. Alternatively, right click **Latest Release** and copy the URL to share it. The suffix of this URL is always `/releases/latest`.
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
|
||||
|
||||
{% else %}
|
||||
|
||||
|
||||
{% endif %}
|
||||
To link directly to a download of your latest release asset that was manually uploaded, link to `/owner/name/releases/latest/download/asset-name.zip`.
|
||||
|
||||
@@ -42,11 +42,11 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.releases %}
|
||||
3. Click **Draft a new release**.
|
||||
|
||||
4. {% ifversion fpt or ghec %}Click **Choose a tag** and type{% else %}Type{% endif %} a version number for your release. Alternatively, select an existing tag.
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}{% else %}{% endif %}
|
||||
4. {% ifversion fpt or ghec %}Click **Choose a tag**, type{% else %}Type{% endif %} a version number for your release{% ifversion fpt or ghec %}, and press **Enter**{% endif %}. Alternatively, select an existing tag.
|
||||
{% ifversion fpt or ghec %}
|
||||
|
||||
1. If you are creating a new tag, click **Create new tag**.
|
||||
5. If you are creating a new tag, click **Create new tag**.
|
||||
|
||||
{% else %}
|
||||
|
||||
@@ -56,7 +56,7 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
|
||||
{% else %}
|
||||
{% endif %}
|
||||
6. Type a title and description for your release.
|
||||
{%- ifversion fpt or ghes > 3.2 or ghae-issue-4972 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4972 %}
|
||||
If you @mention any {% data variables.product.product_name %} users in the description, the published release will include a **Contributors** section with an avatar list of all the mentioned users.
|
||||
{%- endif %}
|
||||
{% ifversion fpt or ghec %} Alternatively, you can automatically generate your release notes by clicking **Auto-generate release notes**.
|
||||
@@ -66,17 +66,21 @@ You can choose whether {% data variables.large_files.product_name_long %} ({% da
|
||||
|
||||
8. To notify users that the release is not ready for production and may be unstable, select **This is a pre-release**.
|
||||
|
||||
{%- ifversion fpt %}
|
||||
1. Optionally, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion.
|
||||
{%- ifversion fpt or ghec %}
|
||||
1. Optionally, if {% data variables.product.prodname_discussions %} are enabled in the repository, select **Create a discussion for this release**, then select the **Category** drop-down menu and click a category for the release discussion.
|
||||
|
||||
{%- endif %}
|
||||
9. If you're ready to publicize your release, click **Publish release**. To work on the release later, click **Save draft**.
|
||||
|
||||
|
||||
{%- ifversion fpt or ghes > 3.2 or ghae-issue-4972 %}
|
||||
{%- ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4972 or ghae-issue-4974 %}
|
||||
You can then view your published or draft releases in the releases feed for your repository. For more information, see "[Viewing your repository's releases and tags](/github/administering-a-repository/releasing-projects-on-github/viewing-your-repositorys-releases-and-tags)."
|
||||
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
|
||||
|
||||
{% else %}
|
||||
|
||||
{% endif %}
|
||||
{%- endif %}
|
||||
|
||||
{% endwebui %}
|
||||
@@ -110,9 +114,14 @@ If you @mention any {% data variables.product.product_name %} users in the notes
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.releases %}
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
|
||||
3. On the right side of the page, next to the release you want to edit, click {% octicon "pencil" aria-label="The edit icon" %}.
|
||||
|
||||
{% else %}
|
||||
3. On the right side of the page, next to the release you want to edit, click **Edit release**.
|
||||
|
||||
4. Edit the details for the release in the form, then click **Update release**.{% ifversion fpt or ghes > 3.2 or ghae-issue-4972 or ghec %} If you add or remove any @mentions of GitHub users in the description, those users will be added or removed from the avatar list in the **Contributors** section of the release.{% endif %}
|
||||
{% endif %}
|
||||
4. Edit the details for the release in the form, then click **Update release**.{% ifversion fpt or ghec or ghes > 3.2 or ghae-issue-4972 %} If you add or remove any @mentions of GitHub users in the description, those users will be added or removed from the avatar list in the **Contributors** section of the release.{% endif %}
|
||||
|
||||
|
||||
{% endwebui %}
|
||||
@@ -131,10 +140,15 @@ Releases cannot currently be edited with {% data variables.product.prodname_cli
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.releases %}
|
||||
{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-4974 %}
|
||||
3. On the right side of the page, next to the release you want to delete, click {% octicon "trash" aria-label="The trash icon" %}.
|
||||
|
||||
{% else %}
|
||||
3. Click the name of the release you wish to delete.
|
||||
|
||||
4. In the upper-right corner of the page, click **Delete**.
|
||||
|
||||
{% endif %}
|
||||
5. Click **Delete this release**.
|
||||
|
||||
|
||||
|
||||
@@ -0,0 +1,31 @@
|
||||
---
|
||||
title: Searching a repository's releases
|
||||
intro: You can use keywords, tags, and other qualifiers to search for particular releases in a repository.
|
||||
permissions: Anyone with read access to a repository can search that repository's releases.
|
||||
shortTitle: Searching releases
|
||||
versions:
|
||||
fpt: '*'
|
||||
ghec: '*'
|
||||
ghes: '>3.2'
|
||||
ghae-issue-4974: '*'
|
||||
topics:
|
||||
- Repositories
|
||||
---
|
||||
|
||||
## Searching for releases in a repository
|
||||
|
||||
{% data reusables.repositories.navigate-to-repo %}
|
||||
{% data reusables.repositories.releases %}
|
||||
1. To search the repository's releases, in the search field at the top of the Releases page, type your query and press **Enter**.
|
||||
|
||||
|
||||
## Search syntax for searching releases in a repository
|
||||
|
||||
You can provide text in your search query which will be matched against the title, body, and tag of the repository's releases. You can also combine the following qualifiers to target specific releases.
|
||||
|
||||
| Qualifier | Example
|
||||
| ------------- | -------------
|
||||
| `draft:true` | **draft:true** will only match draft releases.
|
||||
| `draft:false` | **draft:false** will only match published releases.
|
||||
| <code>tag:<em>TAG</em></code> | **tag:v1** matches a release with the v1 tag and any minor or patch versions within v1, such as v1.0, v1.2, and v1.2.5.
|
||||
| <code>created:<em>DATE</em></code> | **created:2021** will match releases created during 2021. You can also provide date ranges. For more information, see "[Understanding the search syntax](/search-github/getting-started-with-searching-on-github/understanding-the-search-syntax#query-for-dates)."
|
||||
@@ -5,6 +5,7 @@ versions:
|
||||
fpt: '*'
|
||||
ghes: '>=3.1'
|
||||
ghec: '*'
|
||||
ghae: '*'
|
||||
miniTocMaxHeadingLevel: 3
|
||||
---
|
||||
|
||||
|
||||
@@ -21,7 +21,7 @@ To configure{% ifversion ghes = 2.22 %} the beta of{% endif %} {% data variables
|
||||
|
||||
{% endif %}
|
||||
|
||||
You can resize your instance's root disk by building a new instance or using an existing instance. For more information, see "[Increasing storage capacity](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-storage-capacity)."
|
||||
The available space on the root filesystem will be 50% of the total disk size. You can resize your instance's root disk by building a new instance or using an existing instance. For more information, see "[System overview](/enterprise/admin/guides/installation/system-overview#storage-architecture)" and "[Increasing storage capacity](/enterprise/{{ currentVersion }}/admin/guides/installation/increasing-storage-capacity)."
|
||||
|
||||
### CPU and memory
|
||||
|
||||
|
||||
@@ -1,2 +1,2 @@
|
||||
1. To the right of the list of files, click **Releases** or **Latest release**.
|
||||
1. To the right of the list of files, click **Releases**.
|
||||
|
||||
|
||||
@@ -1,5 +1,5 @@
|
||||
{% ifversion fpt or ghec %}
|
||||
For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)" and "[About {% data variables.product.prodname_security_advisories %}](/code-security/security-advisories/about-github-security-advisories)."
|
||||
{% else %}
|
||||
For more information about advisory data, see "<a href="/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database" class="dotcom-only">Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}</a>."
|
||||
For more information about advisory data, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/free-pro-team@latest/code-security/supply-chain-security/browsing-security-vulnerabilities-in-the-github-advisory-database)" in the {% data variables.product.prodname_dotcom_the_website %} documentation.
|
||||
{% endif %}
|
||||
|
||||
@@ -103,6 +103,8 @@
|
||||
/enterprise-cloud@latest/billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise
|
||||
- /billing/managing-your-license-for-github-enterprise/viewing-license-usage-for-github-enterprise
|
||||
|
||||
/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise
|
||||
- /github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account
|
||||
|
||||
# These URLs went from being in free-pro-team to ONLY to being in enterprise-cloud only.
|
||||
# Shipped in pull #20947 on 10/15/21
|
||||
|
||||
@@ -39530,14 +39530,6 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": true,
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
"name": "luke-cage",
|
||||
"note": "The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) for full details. To access the API during the preview period, you must provide a custom [media type](https://docs.github.com/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.luke-cage-preview+json\n```",
|
||||
"html": "<p>The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the <a href=\"https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews\">blog post</a> for full details. To access the API during the preview period, you must provide a custom <a href=\"https://docs.github.com/rest/overview/media-types\">media type</a> in the <code>Accept</code> header:</p>\n<pre><code class=\"hljs language-shell\">application/vnd.github.luke-cage-preview+json</code></pre>"
|
||||
}
|
||||
],
|
||||
"category": "repos",
|
||||
"subcategory": "branches"
|
||||
},
|
||||
|
||||
@@ -1289,6 +1289,8 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": false,
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
@@ -1296,9 +1298,7 @@
|
||||
"note": "The Nested Teams API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2017-08-30-preview-nested-teams) for full details. To access the API, you must provide a custom [media type](https://docs.github.com/enterprise-server@2.22/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.hellcat-preview+json\n```",
|
||||
"html": "<p>The Nested Teams API is currently available for developers to preview. See the <a href=\"https://developer.github.com/changes/2017-08-30-preview-nested-teams\">blog post</a> for full details. To access the API, you must provide a custom <a href=\"https://docs.github.com/enterprise-server@2.22/rest/overview/media-types\">media type</a> in the <code>Accept</code> header:</p>\n<pre><code class=\"hljs language-shell\">application/vnd.github.hellcat-preview+json</code></pre>"
|
||||
}
|
||||
],
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap"
|
||||
]
|
||||
},
|
||||
"slug": "update-ldap-mapping-for-a-team",
|
||||
"category": "enterprise-admin",
|
||||
@@ -33077,6 +33077,8 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": true,
|
||||
"category": "repos",
|
||||
"subcategory": "branches",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
@@ -33084,9 +33086,7 @@
|
||||
"note": "The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) for full details. To access the API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@2.22/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.luke-cage-preview+json\n```",
|
||||
"html": "<p>The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the <a href=\"https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews\">blog post</a> for full details. To access the API during the preview period, you must provide a custom <a href=\"https://docs.github.com/enterprise-server@2.22/rest/overview/media-types\">media type</a> in the <code>Accept</code> header:</p>\n<pre><code class=\"hljs language-shell\">application/vnd.github.luke-cage-preview+json</code></pre>"
|
||||
}
|
||||
],
|
||||
"category": "repos",
|
||||
"subcategory": "branches"
|
||||
]
|
||||
},
|
||||
"slug": "update-pull-request-review-protection",
|
||||
"category": "repos",
|
||||
|
||||
@@ -1289,6 +1289,8 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": false,
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
@@ -1296,9 +1298,7 @@
|
||||
"note": "The Nested Teams API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2017-08-30-preview-nested-teams) for full details. To access the API, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.hellcat-preview+json\n```",
|
||||
"html": "<p>The Nested Teams API is currently available for developers to preview. See the <a href=\"https://developer.github.com/changes/2017-08-30-preview-nested-teams\">blog post</a> for full details. To access the API, you must provide a custom <a href=\"https://docs.github.com/enterprise-server@3.0/rest/overview/media-types\">media type</a> in the <code>Accept</code> header:</p>\n<pre><code class=\"hljs language-shell\">application/vnd.github.hellcat-preview+json</code></pre>"
|
||||
}
|
||||
],
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap"
|
||||
]
|
||||
},
|
||||
"slug": "update-ldap-mapping-for-a-team",
|
||||
"category": "enterprise-admin",
|
||||
@@ -37657,6 +37657,8 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": true,
|
||||
"category": "repos",
|
||||
"subcategory": "branches",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
@@ -37664,9 +37666,7 @@
|
||||
"note": "The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) for full details. To access the API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.luke-cage-preview+json\n```",
|
||||
"html": "<p>The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the <a href=\"https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews\">blog post</a> for full details. To access the API during the preview period, you must provide a custom <a href=\"https://docs.github.com/enterprise-server@3.0/rest/overview/media-types\">media type</a> in the <code>Accept</code> header:</p>\n<pre><code class=\"hljs language-shell\">application/vnd.github.luke-cage-preview+json</code></pre>"
|
||||
}
|
||||
],
|
||||
"category": "repos",
|
||||
"subcategory": "branches"
|
||||
]
|
||||
},
|
||||
"slug": "update-pull-request-review-protection",
|
||||
"category": "repos",
|
||||
|
||||
@@ -1289,6 +1289,8 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": false,
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
@@ -1296,9 +1298,7 @@
|
||||
"note": "The Nested Teams API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2017-08-30-preview-nested-teams) for full details. To access the API, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.hellcat-preview+json\n```",
|
||||
"html": "<p>The Nested Teams API is currently available for developers to preview. See the <a href=\"https://developer.github.com/changes/2017-08-30-preview-nested-teams\">blog post</a> for full details. To access the API, you must provide a custom <a href=\"https://docs.github.com/enterprise-server@3.1/rest/overview/media-types\">media type</a> in the <code>Accept</code> header:</p>\n<pre><code class=\"hljs language-shell\">application/vnd.github.hellcat-preview+json</code></pre>"
|
||||
}
|
||||
],
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap"
|
||||
]
|
||||
},
|
||||
"slug": "update-ldap-mapping-for-a-team",
|
||||
"category": "enterprise-admin",
|
||||
@@ -37794,6 +37794,8 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": true,
|
||||
"category": "repos",
|
||||
"subcategory": "branches",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
@@ -37801,9 +37803,7 @@
|
||||
"note": "The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) for full details. To access the API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.luke-cage-preview+json\n```",
|
||||
"html": "<p>The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the <a href=\"https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews\">blog post</a> for full details. To access the API during the preview period, you must provide a custom <a href=\"https://docs.github.com/enterprise-server@3.1/rest/overview/media-types\">media type</a> in the <code>Accept</code> header:</p>\n<pre><code class=\"hljs language-shell\">application/vnd.github.luke-cage-preview+json</code></pre>"
|
||||
}
|
||||
],
|
||||
"category": "repos",
|
||||
"subcategory": "branches"
|
||||
]
|
||||
},
|
||||
"slug": "update-pull-request-review-protection",
|
||||
"category": "repos",
|
||||
|
||||
@@ -1289,6 +1289,8 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": false,
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
@@ -1296,9 +1298,7 @@
|
||||
"note": "The Nested Teams API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2017-08-30-preview-nested-teams) for full details. To access the API, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.hellcat-preview+json\n```",
|
||||
"html": "<p>The Nested Teams API is currently available for developers to preview. See the <a href=\"https://developer.github.com/changes/2017-08-30-preview-nested-teams\">blog post</a> for full details. To access the API, you must provide a custom <a href=\"https://docs.github.com/enterprise-server@3.2/rest/overview/media-types\">media type</a> in the <code>Accept</code> header:</p>\n<pre><code class=\"hljs language-shell\">application/vnd.github.hellcat-preview+json</code></pre>"
|
||||
}
|
||||
],
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap"
|
||||
]
|
||||
},
|
||||
"slug": "update-ldap-mapping-for-a-team",
|
||||
"category": "enterprise-admin",
|
||||
@@ -39040,6 +39040,8 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": true,
|
||||
"category": "repos",
|
||||
"subcategory": "branches",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
@@ -39047,9 +39049,7 @@
|
||||
"note": "The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) for full details. To access the API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.luke-cage-preview+json\n```",
|
||||
"html": "<p>The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the <a href=\"https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews\">blog post</a> for full details. To access the API during the preview period, you must provide a custom <a href=\"https://docs.github.com/enterprise-server@3.2/rest/overview/media-types\">media type</a> in the <code>Accept</code> header:</p>\n<pre><code class=\"hljs language-shell\">application/vnd.github.luke-cage-preview+json</code></pre>"
|
||||
}
|
||||
],
|
||||
"category": "repos",
|
||||
"subcategory": "branches"
|
||||
]
|
||||
},
|
||||
"slug": "update-pull-request-review-protection",
|
||||
"category": "repos",
|
||||
|
||||
@@ -31163,14 +31163,6 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": true,
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
"name": "luke-cage",
|
||||
"note": "The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) for full details. To access the API during the preview period, you must provide a custom [media type](https://docs.github.com/github-ae@latest/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.luke-cage-preview+json\n```",
|
||||
"html": "<p>The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the <a href=\"https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews\">blog post</a> for full details. To access the API during the preview period, you must provide a custom <a href=\"https://docs.github.com/github-ae@latest/rest/overview/media-types\">media type</a> in the <code>Accept</code> header:</p>\n<pre><code class=\"hljs language-shell\">application/vnd.github.luke-cage-preview+json</code></pre>"
|
||||
}
|
||||
],
|
||||
"category": "repos",
|
||||
"subcategory": "branches"
|
||||
},
|
||||
|
||||
@@ -155634,13 +155634,6 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": true,
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
"name": "luke-cage",
|
||||
"note": "The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) for full details. To access the API during the preview period, you must provide a custom [media type](https://docs.github.com/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.luke-cage-preview+json\n```"
|
||||
}
|
||||
],
|
||||
"category": "repos",
|
||||
"subcategory": "branches"
|
||||
}
|
||||
|
||||
@@ -1462,15 +1462,15 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": false,
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
"name": "hellcat",
|
||||
"note": "The Nested Teams API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2017-08-30-preview-nested-teams) for full details. To access the API, you must provide a custom [media type](https://docs.github.com/enterprise-server@2.22/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.hellcat-preview+json\n```"
|
||||
}
|
||||
],
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap"
|
||||
]
|
||||
}
|
||||
}
|
||||
},
|
||||
@@ -127999,15 +127999,15 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": true,
|
||||
"category": "repos",
|
||||
"subcategory": "branches",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
"name": "luke-cage",
|
||||
"note": "The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) for full details. To access the API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@2.22/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.luke-cage-preview+json\n```"
|
||||
}
|
||||
],
|
||||
"category": "repos",
|
||||
"subcategory": "branches"
|
||||
]
|
||||
}
|
||||
},
|
||||
"delete": {
|
||||
|
||||
@@ -1462,15 +1462,15 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": false,
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
"name": "hellcat",
|
||||
"note": "The Nested Teams API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2017-08-30-preview-nested-teams) for full details. To access the API, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.hellcat-preview+json\n```"
|
||||
}
|
||||
],
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap"
|
||||
]
|
||||
}
|
||||
}
|
||||
},
|
||||
@@ -134164,15 +134164,15 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": true,
|
||||
"category": "repos",
|
||||
"subcategory": "branches",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
"name": "luke-cage",
|
||||
"note": "The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) for full details. To access the API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.0/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.luke-cage-preview+json\n```"
|
||||
}
|
||||
],
|
||||
"category": "repos",
|
||||
"subcategory": "branches"
|
||||
]
|
||||
}
|
||||
},
|
||||
"delete": {
|
||||
|
||||
@@ -1462,15 +1462,15 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": false,
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
"name": "hellcat",
|
||||
"note": "The Nested Teams API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2017-08-30-preview-nested-teams) for full details. To access the API, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.hellcat-preview+json\n```"
|
||||
}
|
||||
],
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap"
|
||||
]
|
||||
}
|
||||
}
|
||||
},
|
||||
@@ -134481,15 +134481,15 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": true,
|
||||
"category": "repos",
|
||||
"subcategory": "branches",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
"name": "luke-cage",
|
||||
"note": "The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) for full details. To access the API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.1/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.luke-cage-preview+json\n```"
|
||||
}
|
||||
],
|
||||
"category": "repos",
|
||||
"subcategory": "branches"
|
||||
]
|
||||
}
|
||||
},
|
||||
"delete": {
|
||||
|
||||
@@ -1462,15 +1462,15 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": false,
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
"name": "hellcat",
|
||||
"note": "The Nested Teams API is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2017-08-30-preview-nested-teams) for full details. To access the API, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.hellcat-preview+json\n```"
|
||||
}
|
||||
],
|
||||
"category": "enterprise-admin",
|
||||
"subcategory": "ldap"
|
||||
]
|
||||
}
|
||||
}
|
||||
},
|
||||
@@ -138101,15 +138101,15 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": true,
|
||||
"category": "repos",
|
||||
"subcategory": "branches",
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
"name": "luke-cage",
|
||||
"note": "The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) for full details. To access the API during the preview period, you must provide a custom [media type](https://docs.github.com/enterprise-server@3.2/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.luke-cage-preview+json\n```"
|
||||
}
|
||||
],
|
||||
"category": "repos",
|
||||
"subcategory": "branches"
|
||||
]
|
||||
}
|
||||
},
|
||||
"delete": {
|
||||
|
||||
@@ -109367,13 +109367,6 @@
|
||||
"x-github": {
|
||||
"githubCloudOnly": false,
|
||||
"enabledForGitHubApps": true,
|
||||
"previews": [
|
||||
{
|
||||
"required": false,
|
||||
"name": "luke-cage",
|
||||
"note": "The Protected Branches API now has a setting for requiring a specified number of approving pull request reviews before merging. This feature is currently available for developers to preview. See the [blog post](https://developer.github.com/changes/2018-03-16-protected-branches-required-approving-reviews) for full details. To access the API during the preview period, you must provide a custom [media type](https://docs.github.com/github-ae@latest/rest/overview/media-types) in the `Accept` header:\n```shell\napplication/vnd.github.luke-cage-preview+json\n```"
|
||||
}
|
||||
],
|
||||
"category": "repos",
|
||||
"subcategory": "branches"
|
||||
}
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:dbb4342cc295422328f2187745cf43d8880abedc4eaf652ace5f479fef433301
|
||||
size 434696
|
||||
oid sha256:b45f9bb50a3466cb68a9e30378de5743810d781d402d8cf33821974c8078aa4e
|
||||
size 434741
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:2f8d8ce9ab094cf85124a944e4240720bd28d91f23f53516e50e4863384d9bb2
|
||||
size 1702398
|
||||
oid sha256:e24f4906c91d2f1ebd82b143c5f5b0abd3f4ada4e1a2d907460e8a8a53b9f7e5
|
||||
size 1702344
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:1333de9978b1ed632355024a0d9ca2600aaeef9713c87626286c4af460ce2fba
|
||||
size 456833
|
||||
oid sha256:d353443d451656d62fb6f4b55cc7af03aee97e8988ae31d75a4513dea9363148
|
||||
size 457889
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:fc90c48335755257793d8980d74adfd9719ffd60282a77b9b60cda768fcef649
|
||||
size 1782983
|
||||
oid sha256:56a9809e46784cc4e4ecda68e181607ed9f9add7db41a616a2a451d711dcbd02
|
||||
size 1784784
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:92f223286344a4caab813cec39ee8f8667820dfc7c992253170e070e988b3f11
|
||||
size 467601
|
||||
oid sha256:2dbcc6e153eff1d8ff4973cb7e9e0827cf44d7af476cfa488061c966386e5707
|
||||
size 468221
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:4cf31ffda277e0a8e8d1018ca2824d5cf6389938587a165abef724bae2f9968e
|
||||
size 1827503
|
||||
oid sha256:2c7195b175ea6c8f09407a5ca165dd90861e70cb9d8370758b5f3503c2f68907
|
||||
size 1827585
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:fd707c5adc629d2bc00a354a57c6c9c1c5d9e704bdc9497f7e60f44d4d4d1915
|
||||
size 475702
|
||||
oid sha256:d5e053af5c8211ab0cff4d7399236fc65e5df5937e21e56aa840663ed6da8b29
|
||||
size 476104
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:6277cbaf6fda96d2a205443fa5eb2251e7d07ca95f3bcbf2e6bdeeeb7bc10f1e
|
||||
size 1859261
|
||||
oid sha256:9586dd825007da5b715bc4ffdc8502a96dfa92ab4c5567d6f9af76be0d883253
|
||||
size 1860001
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:5ae60373b6b82ff23f84a010f44b551df2253fecafff06b6d005a9fb40232fc2
|
||||
size 780805
|
||||
oid sha256:b6d12830319067cf6d96dc43d8aee2b85011be305bdbbeb43445bed9dadc6243
|
||||
size 780663
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:6972428a784c3b9ac09e9e9ae860f14708e7e2949aedf70e20335b9882db3676
|
||||
size 1228745
|
||||
oid sha256:a23b827f492a41f52b16adf9ca0f2b5650dfd2f8000b4b2091072f7de5dc485e
|
||||
size 1228642
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:5f63eea272b693a71007ab39ba6274d54ab57a4dd8b716ccf09f59cbe15e275e
|
||||
size 622732
|
||||
oid sha256:2ed747b63d63b27806b761d248a855bdb7688133ee9a3ab49ee9bc800eb07707
|
||||
size 623063
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:78485ed38f2d1d9e514d73ade5b23cfab69cd51020d22b910efb9981d46dd1c0
|
||||
size 2338480
|
||||
oid sha256:5d74d1ba19db27963bdb3b64879c6094921b2232bf53315099d7e8488c8ccda7
|
||||
size 2339336
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:fcaa0a12268004adadfd0286c9a746b8f6b3f882156cff9ff048fdb32435915c
|
||||
size 365832
|
||||
oid sha256:1eb8bff4ce913cb7dd93a831c2655198177c48ad30d04b94b8ab7819900a0607
|
||||
size 365911
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:daec1b5195d09c7411c411f48fd849c57926ff12b97b0ffff217f73d02c30f13
|
||||
size 1363995
|
||||
oid sha256:c0e6f579764ec891099ea5588ed915672c0ae5a943392a37386484149978a5df
|
||||
size 1364964
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:37f4319ce04924013ca858eba5ef023241265d2cb7567a610ab6e8d6733d411d
|
||||
size 549485
|
||||
oid sha256:c23016a6563dba76c9383221e70bec6009a8067cc3592818586574d3eca9fb70
|
||||
size 549584
|
||||
|
||||
@@ -1,3 +1,3 @@
|
||||
version https://git-lfs.github.com/spec/v1
|
||||
oid sha256:9df6675d562d8e59332e2e9861a0026b16366f7d3e1027deeab66035ca48ebf3
|
||||
size 2163751
|
||||
oid sha256:ef565ce7ddb82b66b950888e713f0f9f723f4b08af10699d940adefae04eea2b
|
||||
size 2165263
|
||||
|
||||
2966
package-lock.json
generated
2966
package-lock.json
generated
File diff suppressed because it is too large
Load Diff
28
package.json
28
package.json
@@ -32,7 +32,7 @@
|
||||
"dotenv": "^10.0.0",
|
||||
"express": "^4.17.1",
|
||||
"express-basic-auth": "^1.2.0",
|
||||
"express-rate-limit": "^5.4.1",
|
||||
"express-rate-limit": "^5.5.0",
|
||||
"express-timeout-handler": "^2.2.2",
|
||||
"flat": "^5.0.2",
|
||||
"github-slugger": "^1.4.0",
|
||||
@@ -44,7 +44,7 @@
|
||||
"hast-util-to-string": "^2.0.0",
|
||||
"hastscript": "^7.0.2",
|
||||
"helmet": "^4.6.0",
|
||||
"highlight.js": "^11.2.0",
|
||||
"highlight.js": "^11.3.1",
|
||||
"highlightjs-graphql": "^1.0.2",
|
||||
"hot-shots": "^8.5.2",
|
||||
"html-entities": "^2.3.2",
|
||||
@@ -56,7 +56,7 @@
|
||||
"lodash-es": "^4.17.21",
|
||||
"lunr": "^2.3.9",
|
||||
"lunr-languages": "^1.9.0",
|
||||
"mdast-util-from-markdown": "^1.0.3",
|
||||
"mdast-util-from-markdown": "^1.0.4",
|
||||
"mdast-util-to-string": "^3.1.0",
|
||||
"morgan": "^1.10.0",
|
||||
"next": "^11.1.2",
|
||||
@@ -78,10 +78,10 @@
|
||||
"rehype-stringify": "^9.0.2",
|
||||
"remark-code-extra": "^1.0.1",
|
||||
"remark-gemoji-to-emoji": "^1.1.0",
|
||||
"remark-gfm": "^2.0.0",
|
||||
"remark-gfm": "^3.0.0",
|
||||
"remark-parse": "^10.0.0",
|
||||
"remark-parse-no-trim": "^8.0.4",
|
||||
"remark-rehype": "^9.0.0",
|
||||
"remark-rehype": "^10.0.0",
|
||||
"revalidator": "^0.3.1",
|
||||
"rss-parser": "^3.12.0",
|
||||
"scroll-anchoring": "^0.1.0",
|
||||
@@ -97,12 +97,12 @@
|
||||
"walk-sync": "^3.0.0"
|
||||
},
|
||||
"devDependencies": {
|
||||
"@actions/core": "^1.5.0",
|
||||
"@actions/core": "^1.6.0",
|
||||
"@actions/github": "^5.0.0",
|
||||
"@babel/core": "^7.15.8",
|
||||
"@babel/eslint-parser": "^7.15.8",
|
||||
"@babel/plugin-syntax-top-level-await": "^7.14.5",
|
||||
"@babel/plugin-transform-runtime": "^7.15.0",
|
||||
"@babel/plugin-transform-runtime": "^7.15.8",
|
||||
"@babel/preset-env": "^7.15.8",
|
||||
"@graphql-inspector/core": "^2.9.0",
|
||||
"@graphql-tools/load": "^7.3.2",
|
||||
@@ -110,9 +110,9 @@
|
||||
"@octokit/rest": "^18.12.0",
|
||||
"@types/github-slugger": "^1.3.0",
|
||||
"@types/imurmurhash": "^0.1.1",
|
||||
"@types/js-cookie": "^2.2.7",
|
||||
"@types/js-cookie": "^3.0.0",
|
||||
"@types/lodash": "^4.14.175",
|
||||
"@types/react": "^17.0.27",
|
||||
"@types/react": "^17.0.30",
|
||||
"@types/react-dom": "^17.0.9",
|
||||
"@types/react-syntax-highlighter": "^13.5.2",
|
||||
"@types/uuid": "^8.3.1",
|
||||
@@ -121,7 +121,7 @@
|
||||
"async": "^3.2.1",
|
||||
"await-sleep": "0.0.1",
|
||||
"babel-loader": "^8.2.2",
|
||||
"babel-plugin-styled-components": "^1.13.2",
|
||||
"babel-plugin-styled-components": "^1.13.3",
|
||||
"babel-preset-env": "^1.7.0",
|
||||
"chalk": "^4.1.2",
|
||||
"commander": "^8.2.0",
|
||||
@@ -134,7 +134,7 @@
|
||||
"eslint": "^7.32.0",
|
||||
"eslint-config-prettier": "^8.3.0",
|
||||
"eslint-config-standard": "^16.0.3",
|
||||
"eslint-plugin-import": "^2.24.2",
|
||||
"eslint-plugin-import": "^2.25.2",
|
||||
"eslint-plugin-jsx-a11y": "^6.4.1",
|
||||
"eslint-plugin-node": "^11.1.0",
|
||||
"eslint-plugin-promise": "^5.1.0",
|
||||
@@ -148,7 +148,7 @@
|
||||
"is-url": "^1.2.4",
|
||||
"japanese-characters": "^1.1.0",
|
||||
"javascript-stringify": "^2.1.0",
|
||||
"jest": "^27.2.5",
|
||||
"jest": "^27.3.0",
|
||||
"jest-github-actions-reporter": "^1.0.3",
|
||||
"jest-slow-test-reporter": "^1.0.0",
|
||||
"linkinator": "^2.14.4",
|
||||
@@ -168,11 +168,11 @@
|
||||
"rimraf": "^3.0.2",
|
||||
"robots-parser": "^2.3.0",
|
||||
"run-script-os": "^1.1.6",
|
||||
"sass": "^1.39.2",
|
||||
"sass": "^1.43.2",
|
||||
"start-server-and-test": "^1.14.0",
|
||||
"strip-ansi": "^7.0.1",
|
||||
"supertest": "^6.1.6",
|
||||
"typescript": "^4.4.3",
|
||||
"typescript": "^4.4.4",
|
||||
"url-template": "^2.0.8",
|
||||
"website-scraper": "^4.2.3",
|
||||
"yesno": "^0.3.1"
|
||||
|
||||
Reference in New Issue
Block a user