Skip to content

Commit 44a609d

Browse files
jc-clarklecoursen
andauthored
Enterprise bug fixes for the week of June 19, 2023 (#38403)
Co-authored-by: Laura Coursen <[email protected]>
1 parent 32af69c commit 44a609d

File tree

8 files changed

+44
-10
lines changed

8 files changed

+44
-10
lines changed

content/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-your-personal-account/managing-multiple-accounts.md

+12
Original file line numberDiff line numberDiff line change
@@ -53,6 +53,10 @@ Alternatively, if you want to use the HTTPS protocol for both accounts, you can
5353
```
5454

5555
{% data reusables.git.clear-stored-gcm-credentials %}
56+
57+
```shell copy
58+
echo "protocol=https\nhost=github.com" | git credential-manager erase
59+
```
5660
{% data reusables.git.cache-on-repository-path %}
5761
{% data reusables.accounts.create-personal-access-tokens %}
5862
{% data reusables.git.provide-credentials %}
@@ -66,6 +70,10 @@ Alternatively, if you want to use the HTTPS protocol for both accounts, you can
6670
{% data reusables.git.clear-the-stored-credentials %}
6771
{% data reusables.git.no-credential-manager %}
6872
{% data reusables.git.clear-stored-gcm-credentials %}
73+
74+
```shell copy
75+
echo "protocol=https`nhost=github.com" | git credential-manager erase
76+
```
6977
- If the output is `wincred`, you're using the Windows Credential Manager. To clear the credentials, enter the following command.
7078
7179
```shell copy
@@ -85,6 +93,10 @@ Alternatively, if you want to use the HTTPS protocol for both accounts, you can
8593
{% data reusables.git.clear-the-stored-credentials %}
8694
{% data reusables.git.no-credential-manager %}
8795
{% data reusables.git.clear-stored-gcm-credentials %}
96+
97+
```shell copy
98+
echo "protocol=https\nhost=github.com" | git credential-manager erase
99+
```
88100
{% data reusables.git.cache-on-repository-path %}
89101
{% data reusables.accounts.create-personal-access-tokens %}
90102
{% data reusables.git.provide-credentials %}

content/admin/configuration/configuring-your-enterprise/configuring-backups-on-your-appliance.md

+6-1
Original file line numberDiff line numberDiff line change
@@ -159,6 +159,8 @@ If your installation is in a Git repository, you can install the latest version
159159

160160
If your backup host has internet connectivity and you previously used a compressed archive (`.tar.gz`) to install or upgrade {% data variables.product.prodname_enterprise_backup_utilities %}, we recommend using a Git repository for your installation instead. Upgrading using Git requires less work and preserves your backup configuration.
161161

162+
To use Git instead of a compressed archive for upgrades, you must back up your existing configuration, clone the repository, copy your configuration into place, verify the installation, verify SSH connectivity, then delete the old installation.
163+
162164
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-directory %}
163165
1. To back up your existing {% data variables.product.prodname_enterprise_backup_utilities %} configuration, copy your current `backup.config` file to a safe location, such as your home directory.
164166

@@ -185,7 +187,7 @@ If your backup host has internet connectivity and you previously used a compress
185187
```
186188
cp PATH/TO/BACKUP/FROM/STEP/2 backup.config
187189
```
188-
190+
189191
{% note %}
190192

191193
**Note:** You can choose where to restore your backup configuration file to after cloning. For more information about where configuration files can be located, see [Getting started](https://github.com/github/backup-utils/blob/master/docs/getting-started.md) in the {% data variables.product.prodname_enterprise_backup_utilities %} project documentation.
@@ -194,6 +196,9 @@ If your backup host has internet connectivity and you previously used a compress
194196

195197
1. To confirm that the paths to directories or scripts in your backup configuration file are correct, review the file in a text editor.
196198
{% data reusables.enterprise_backup_utilities.enterprise-backup-utils-verify-upgrade %}
199+
200+
1. Confirm that your backup data is not in the directory for the old installation.
201+
197202
1. Delete your old GitHub Enterprise Server Backup Utilities directory from step 1 (where the compressed archive installation was located).
198203

199204
## Scheduling a backup

content/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/streaming-the-audit-log-for-your-enterprise.md

+1-5
Original file line numberDiff line numberDiff line change
@@ -39,11 +39,7 @@ The benefits of streaming audit data include:
3939

4040
Enterprise owners can set up{% ifversion pause-audit-log-stream %}, pause,{% endif %} or delete a stream at any time. The stream exports the audit and Git events data for all of the organizations in your enterprise.
4141

42-
{% note %}
43-
44-
**Note:** All audit logs are streamed in JSON format.
45-
46-
{% endnote %}
42+
All streamed audit logs are sent as compressed JSON files. The filename format is in`YYYY/MM/HH/MM/<uuid>.json.gz`.
4743

4844
## Setting up audit log streaming
4945

content/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise.md

+6
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,12 @@ shortTitle: About licenses
1515

1616
{% data reusables.enterprise.about-deployment-methods %}
1717

18+
{% ifversion ghec %}
19+
20+
{% data reusables.enterprise.invoiced-customer-to-access-ghes %}
21+
22+
{% endif %}
23+
1824
{% data reusables.enterprise-licensing.unique-user-licensing-model %}
1925

2026
To ensure the same user isn't consuming more than one license for multiple enterprise deployments, you can synchronize license usage between your {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %} deployments.

content/billing/managing-your-license-for-github-enterprise/downloading-your-license-for-github-enterprise.md

+6
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,12 @@ shortTitle: Download your license
1616

1717
After you purchase or upgrade a license for {% data variables.product.prodname_enterprise %} from {% data variables.contact.contact_enterprise_sales %}, you must download your new license file. For more information about licenses for {% data variables.product.prodname_enterprise %}, see "[AUTOTITLE](/billing/managing-your-license-for-github-enterprise/about-licenses-for-github-enterprise)."
1818

19+
{% ifversion ghec %}
20+
21+
{% data reusables.enterprise.invoiced-customer-to-access-ghes %}
22+
23+
{% endif %}
24+
1925
{% data reusables.enterprise-licensing.contact-sales-for-renewals-or-seats %}
2026

2127
## Downloading your license file

content/organizations/managing-organization-settings/creating-an-announcement-banner-for-your-organization.md

+8
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,14 @@ topics:
99
- Maintenance
1010
---
1111

12+
{% ifversion ghec %}
13+
{% note %}
14+
15+
**Note:** To create an announcement banner, your organization must use {% data variables.product.prodname_ghe_cloud %}. {% data reusables.enterprise.link-to-ghec-trial %}
16+
17+
{% endnote %}
18+
{% endif %}
19+
1220
You can create an announcement banner that will be displayed to all organization members at the top of every page in the organization.
1321

1422
{% data reusables.enterprise.user-messages-markdown %}
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
{% note %}
2+
3+
**Note:** Only invoiced customers can access {% data variables.product.prodname_ghe_server %}. To switch to invoicing, contact {% data variables.contact.contact_enterprise_sales %}.
4+
5+
{% endnote %}
Original file line numberDiff line numberDiff line change
@@ -1,5 +1 @@
11
- If the output is `manager-core`, you're using Git Credential Manager. To clear the credentials, run the following command.
2-
3-
```shell copy
4-
git credential-manager reject https://github.com
5-
```

0 commit comments

Comments
 (0)