Skip to content

Commit f5df18d

Browse files
author
Martin Lopes
authored
Merge branch 'main' into thejoebourneidentity-self-hosted-architectures
2 parents 8e2b1e8 + a982256 commit f5df18d

2,782 files changed

Lines changed: 27340 additions & 16461 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
20.5 KB
Loading
49.7 KB
Loading
-75 Bytes
Loading

content/admin/enterprise-management/upgrading-github-enterprise-server.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,26 @@ versions:
2929

3030
{% endnote %}
3131

32+
{% if currentVersion ver_gt "enterprise-server@2.20" and currentVersion ver_lt "enterprise-server@3.2" %}
33+
34+
### About minimum requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later
35+
36+
Before upgrading to {% data variables.product.prodname_ghe_server %} 3.0 or later, review the hardware resources you've provisioned for your instance. {% data variables.product.prodname_ghe_server %} 3.0 introduces new features such as {% data variables.product.prodname_actions %} and {% data variables.product.prodname_registry %}, and requires more resources than versions 2.22 and earlier. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes).
37+
38+
Increased requirements for {% data variables.product.prodname_ghe_server %} 3.0 and later are **bold** in the following table.
39+
40+
| User licenses | vCPUs | Memory | Attached storage | Root storage |
41+
| :- | -: | -: | -: | -: |
42+
| Trial, demo, or 10 light users | **4**<br/>_Up from 2_ | **32 GB**<br/>_Up from 16 GB_ | **150 GB**<br/>_Up from 100 GB_ | 200 GB |
43+
| 10 to 3,000 | **8**<br/>_Up from 4_ | **48 GB**<br/>_Up from 32 GB_ | **300 GB**<br/>_Up from 250 GB_ | 200 GB |
44+
| 3,000 to 5000 | **12**<br/>_Up from 8_ | 64 GB | 500 GB | 200 GB |
45+
| 5,000 to 8000 | **16**<br/>_Up from 12_ | 96 GB | 750 GB | 200 GB |
46+
| 8,000 to 10,000+ | **20**<br/>_Up from 16_ | **160 GB**<br/>_Up from 128 GB_ | 1000 GB | 200 GB |
47+
48+
{% data reusables.enterprise_installation.about-adjusting-resources %}
49+
50+
{% endif %}
51+
3252
### Taking a snapshot
3353

3454
A snapshot is a checkpoint of a virtual machine (VM) at a point in time. We highly recommend taking a snapshot before upgrading your virtual machine so that if an upgrade fails, you can revert your VM back to the snapshot. If you're upgrading to a new feature release, you must take a VM snapshot. If you're upgrading to a patch release, you can attach the existing data disk.

content/admin/github-actions/getting-started-with-github-actions-for-github-enterprise-server.md

Lines changed: 25 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -9,26 +9,42 @@ versions:
99
enterprise-server: '>=2.22'
1010
---
1111

12-
{% if currentVersion == "enterprise-server@2.22" %}
13-
{% note %}
14-
15-
**Note:** {% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. Review the external storage requirements below and [sign up for the beta](https://resources.github.com/beta-signup/).
16-
17-
{% endnote %}
18-
{% endif %}
12+
{% data reusables.actions.enterprise-beta %}
1913

2014
{% data reusables.actions.enterprise-github-hosted-runners %}
2115

2216
{% if currentVersion ver_gt "enterprise-server@2.22" %}
2317

2418
This article explains how site administrators can configure {% data variables.product.prodname_ghe_server %} to use {% data variables.product.prodname_actions %}. It covers the hardware and software requirements, presents the storage options, and describes the security management policies.
2519

20+
{% endif %}
21+
2622
### Review hardware considerations
2723

28-
{% data reusables.actions.enterprise-hardware-considerations %}
24+
{% if currentVersion == "enterprise-server@2.22" or currentVersion == "enterprise-server@3.0" %}
25+
26+
{% note %}
27+
28+
**Note**: {% if currentVersion == "enterprise-server@2.22" %}{% data variables.product.prodname_actions %} was available for {% data variables.product.prodname_ghe_server %} 2.22 as a limited beta. {% endif %}If you're upgrading an existing {% data variables.product.prodname_ghe_server %} instance to 3.0 or later and want to configure {% data variables.product.prodname_actions %}, note that the minimum hardware requirements have increased. For more information, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server#about-minimum-requirements-for-github-enterprise-server-30-and-later)."
29+
30+
{% endnote %}
2931

3032
{% endif %}
3133

34+
{% data reusables.actions.enterprise-hardware-considerations %}
35+
36+
For more information about resource requirements for {% data variables.product.prodname_ghe_server %}, see the hardware considerations for your instance's platform.
37+
38+
- [AWS](/admin/installation/installing-github-enterprise-server-on-aws#hardware-considerations)
39+
- [Azure](/admin/installation/installing-github-enterprise-server-on-azure#hardware-considerations)
40+
- [Google Cloud Platform](/admin/installation/installing-github-enterprise-server-on-google-cloud-platform#hardware-considerations)
41+
- [Hyper-V](/admin/installation/installing-github-enterprise-server-on-hyper-v#hardware-considerations)
42+
- [OpenStack KVM](/admin/installation/installing-github-enterprise-server-on-openstack-kvm#hardware-considerations)
43+
- [VMware](/admin/installation/installing-github-enterprise-server-on-vmware#hardware-considerations)
44+
- [XenServer](/admin/installation/installing-github-enterprise-server-on-xenserver#hardware-considerations)
45+
46+
{% data reusables.enterprise_installation.about-adjusting-resources %}
47+
3248
### External storage requirements
3349

3450
To enable {% data variables.product.prodname_actions %} on {% data variables.product.prodname_ghe_server %}, you must have access to external blob storage.
@@ -55,7 +71,7 @@ To enable {% data variables.product.prodname_actions %} on {% data variables.pro
5571

5672
### Enabling {% data variables.product.prodname_actions %}
5773

58-
{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 is a limited public beta. [Sign up for the beta](https://resources.github.com/beta-signup/).
74+
{% data variables.product.prodname_actions %} support on {% data variables.product.prodname_ghe_server %} 2.22 was available as a limited beta. To configure {% data variables.product.prodname_actions %} for your instance, upgrade to {% data variables.product.prodname_ghe_server %} 3.0 or later. For more information, see the [{% data variables.product.prodname_ghe_server %} 3.0 release notes](/enterprise-server@3.0/admin/release-notes) and "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/upgrading-github-enterprise-server)."
5975

6076
### Further reading
6177

content/github/administering-a-repository/about-dependabot-version-updates.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@ title: About Dependabot version updates
33
intro: 'You can use {% data variables.product.prodname_dependabot %} to keep the packages you use updated to the latest versions.'
44
redirect_from:
55
- /github/administering-a-repository/about-dependabot
6+
- /github/administering-a-repository/about-github-dependabot
67
- /github/administering-a-repository/about-github-dependabot-version-updates
78

89
versions:

content/github/authenticating-to-github/associating-an-email-with-your-gpg-key.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,14 +32,18 @@ If you're using a GPG key that matches your committer identity and your verified
3232
Comment: <em>GitHub key</em>
3333
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit?
3434
```
35-
7. Enter `O` to save your selections.
35+
7. Enter `O` to confirm your selections.
3636
8. Enter your key's passphrase.
37-
9. Enter `gpg --armor --export GPG key ID`, substituting in the GPG key ID you'd like to use. In the following example, the GPG key ID is `3AA5C34371567BD2`:
37+
9. Enter `gpg> save` to save the changes
38+
```shell
39+
$ gpg> save
40+
```
41+
10. Enter `gpg --armor --export GPG key ID`, substituting in the GPG key ID you'd like to use. In the following example, the GPG key ID is `3AA5C34371567BD2`:
3842
```shell
3943
$ gpg --armor --export <em>3AA5C34371567BD2</em>
4044
# Prints the GPG key, in ASCII armor format
4145
```
42-
10. Upload the GPG key by [adding it to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account).
46+
11. Upload the GPG key by [adding it to your GitHub account](/articles/adding-a-new-gpg-key-to-your-github-account).
4347

4448
### Further reading
4549

content/github/creating-cloning-and-archiving-repositories/about-code-owners.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ When someone with admin or owner permissions has enabled required reviews, they
2323

2424
{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.19" %}If a team has enabled code review assignments, the individual approvals won't satisfy the requirement for code owner approval in a protected branch. For more information, see "[Managing code review assignment for your team](/github/setting-up-and-managing-organizations-and-teams/managing-code-review-assignment-for-your-team)."{% endif %}
2525

26-
{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
26+
{% if currentVersion == "free-pro-team@latest" or currentVersion == "github-ae@latest" or currentVersion ver_gt "enterprise-server@2.22" %}
2727
If a file has a code owner, you can see who the code owner is before you open a pull request. In the repository, you can browse to the file and hover over {% octicon "shield-lock" aria-label="The edit icon" %}.
2828

2929
![Code owner for a file in a repository](/assets/images/help/repository/code-owner-for-a-file.png)

content/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-codeql-code-scanning-in-your-ci-system.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -147,6 +147,9 @@ Analyzes the code in the {% data variables.product.prodname_codeql %} databases
147147
| <nobr>`--checkout-path`</nobr> | | The path to the checkout of your repository. The default is the current working directory. |
148148
| `--no-upload` | | None. Stops the {% data variables.product.prodname_codeql_runner %} from uploading the results to {% data variables.product.product_location %}. |
149149
| `--output-dir` | | Directory where the output SARIF files are stored. The default is in the directory of temporary files. |
150+
| `--ram` | | Amount of memory to use when running queries. The default is to use all available memory. |
151+
| `--no-add-snippets` | | None. Includes code snippets in the SARIF output. |
152+
| `--threads` | | Number of threads to use when running queries. The default is to use all available cores. |
150153
| `--temp-dir` | | Directory where temporary files are stored. The default is _./codeql-runner_. |
151154
| `--debug` | | None. Prints more verbose output. |
152155
| `-h`, `--help` | | None. Displays help for the command. |

content/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ When {% data variables.product.product_name %} identifies a vulnerable dependenc
7272

7373
### Access to {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}{% data variables.product.prodname_dependabot %}{% else %}security{% endif %} alerts
7474

75-
You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/articles/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
75+
You can see all of the alerts that affect a particular project{% if currentVersion == "free-pro-team@latest" %} on the repository's Security tab or{% endif %} in the repository's dependency graph.{% if currentVersion == "free-pro-team@latest" %} For more information, see "[Viewing and updating vulnerable dependencies in your repository](/github/managing-security-vulnerabilities/viewing-and-updating-vulnerable-dependencies-in-your-repository)."{% endif %}
7676

7777
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.21" %}
7878
By default, we notify people with admin permissions in the affected repositories about new {% data variables.product.prodname_dependabot_alerts %}.{% endif %} {% if currentVersion == "free-pro-team@latest" %}{% data variables.product.product_name %} never publicly discloses identified vulnerabilities for any repository. You can also make {% data variables.product.prodname_dependabot_alerts %} visible to additional people or teams working repositories that you own or have admin permissions for. For more information, see "[Managing security and analysis settings for your repository](/github/administering-a-repository/managing-security-and-analysis-settings-for-your-repository#granting-access-to-security-alerts)."
@@ -84,6 +84,10 @@ We send security alerts to people with admin permissions in the affected reposit
8484

8585
{% data reusables.notifications.vulnerable-dependency-notification-delivery-method-customization %}{% if enterpriseServerVersions contains currentVersion and currentVersion ver_lt "enterprise-server@2.21" %} For more information, see "[Choosing the delivery method for your notifications](/github/receiving-notifications-about-activity-on-github/choosing-the-delivery-method-for-your-notifications)."{% endif %}{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.20" %} For more information, see "[Configuring notifications for vulnerable dependencies](/github/managing-security-vulnerabilities/configuring-notifications-for-vulnerable-dependencies)."{% endif %}
8686

87+
{% if currentVersion == "free-pro-team@latest" %}
88+
You can also see all the {% data variables.product.prodname_dependabot_alerts %} that correspond to a particular vulnerability in the {% data variables.product.prodname_advisory_database %}. For more information, see "[Browsing security vulnerabilities in the {% data variables.product.prodname_advisory_database %}](/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database#viewing-your-vulnerable-repositories)."
89+
{% endif %}
90+
8791
{% if currentVersion == "free-pro-team@latest" %}
8892
### Further reading
8993

0 commit comments

Comments
 (0)