Enterprise bug fixes for 2023-11-20 (#46433)
This commit is contained in:
Matt Pollard
@@ -30,7 +30,7 @@ After you configure the connection between {% data variables.location.product_lo
|
||||
| ----------- | ----------- | ----------- |{% ifversion ghes %}
|
||||
Automatic user license sync | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.location.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[AUTOTITLE](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae %}
|
||||
{% data variables.product.prodname_dependabot %} | Allow users to find and fix vulnerabilities in code dependencies. | "[AUTOTITLE](/admin/configuration/configuring-github-connect/enabling-dependabot-for-your-enterprise)"{% endif %}
|
||||
{% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files. | "[AUTOTITLE](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% ifversion server-statistics %}
|
||||
{% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in public workflow files. | "[AUTOTITLE](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)"{% ifversion server-statistics %}
|
||||
{% data variables.product.prodname_server_statistics %} | Analyze your own aggregate data from GitHub Enterprise Server, and help us improve GitHub products. | "[AUTOTITLE](/admin/configuration/configuring-github-connect/enabling-server-statistics-for-your-enterprise)"{% endif %}
|
||||
Unified search | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.location.product_location %}. | "[AUTOTITLE](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)"
|
||||
Unified contributions | Allow users to include anonymized contribution counts for their work on {% data variables.location.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}. | "[AUTOTITLE](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)"
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
---
|
||||
title: Enabling automatic access to GitHub.com actions using GitHub Connect
|
||||
intro: 'To allow {% data variables.product.prodname_actions %} in your enterprise to use actions from {% data variables.product.prodname_dotcom_the_website %}, you can connect your enterprise instance to {% data variables.product.prodname_ghe_cloud %}.'
|
||||
permissions: 'Enterprise owners can enable access to all {% data variables.product.prodname_dotcom_the_website %} actions.'
|
||||
permissions: 'Enterprise owners can enable access to public {% data variables.product.prodname_dotcom_the_website %} actions.'
|
||||
redirect_from:
|
||||
- /enterprise/admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
|
||||
- /admin/github-actions/enabling-automatic-access-to-githubcom-actions-using-github-connect
|
||||
@@ -33,9 +33,9 @@ Alternatively, if you want stricter control over which actions are allowed in yo
|
||||
If a user has already created an organization and repository in your enterprise that matches an organization and repository name on {% data variables.product.prodname_dotcom_the_website %}, the repository on your enterprise will be used instead of the {% data variables.product.prodname_dotcom_the_website %} repository. {% ifversion ghae %}A malicious user could take advantage of this behavior to run code as part of a workflow.{% else %}For more information, see "[Automatic retirement of namespaces for actions accessed on {% data variables.product.prodname_dotcom_the_website%}](#automatic-retirement-of-namespaces-for-actions-accessed-on-githubcom)."
|
||||
{% endif %}
|
||||
|
||||
## Enabling automatic access to all {% data variables.product.prodname_dotcom_the_website %} actions
|
||||
## Enabling automatic access to public {% data variables.product.prodname_dotcom_the_website %} actions
|
||||
|
||||
Before enabling access to all actions from {% data variables.product.prodname_dotcom_the_website %} for your enterprise, you must{% ifversion ghes %}:
|
||||
Before enabling access to public actions from {% data variables.product.prodname_dotcom_the_website %} for your enterprise, you must{% ifversion ghes %}:
|
||||
- Configure {% data variables.location.product_location %} to use {% data variables.product.prodname_actions %}. For more information, see "[AUTOTITLE](/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/getting-started-with-github-actions-for-github-enterprise-server)."
|
||||
- Enable{% else %} enable{% endif %} {% data variables.product.prodname_github_connect %}. For more information, see "[AUTOTITLE](/admin/configuration/configuring-github-connect/managing-github-connect)."
|
||||
|
||||
|
||||
@@ -144,7 +144,9 @@ To discover how a member was added to an organization, you can filter the member
|
||||
|
||||
## Authenticating with a {% data variables.enterprise.prodname_managed_user %}
|
||||
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} must authenticate through their IdP. To authenticate, a {% data variables.enterprise.prodname_managed_user %} can visit their IdP application portal or use the login page on {% data variables.product.prodname_dotcom_the_website %}.
|
||||
{% data variables.enterprise.prodname_managed_users_caps %} must authenticate through your IdP. The way that {% data variables.enterprise.prodname_managed_users %} authenticate depends on whether you configure SAML or OIDC authentication.
|
||||
|
||||
If your enterprise is configured for SAML authentication, a {% data variables.enterprise.prodname_managed_user %} can access your enterprise by visiting their IdP application portal. If your enterprise is configured for OIDC authentication, a {% data variables.enterprise.prodname_managed_user %} can access your enterprise by using the login page on {% data variables.product.prodname_dotcom_the_website %}. IdP-initiated authentication is not currently supported for OIDC. In either configuration, a {% data variables.enterprise.prodname_managed_user %} can initiate authentication directly from the organization or enterprise's page on {% data variables.location.product_location %}.
|
||||
|
||||
By default, when an unauthenticated user attempts to access an enterprise that uses {% data variables.product.prodname_emus %}, {% data variables.product.company_short %} displays a 404 error. An enterprise owner can optionally enable automatic redirects to single sign-on (SSO) instead of the 404. For more information, see "[AUTOTITLE](/enterprise-cloud@latest/admin/policies/enforcing-policies-for-your-enterprise/enforcing-policies-for-security-settings-in-your-enterprise#managing-sso-for-unauthenticated-users)."
|
||||
|
||||
|
||||
@@ -27,10 +27,7 @@ permissions: Enterprise owners can configure audit log streaming.
|
||||
|
||||
## About audit log streaming
|
||||
|
||||
To help protect your intellectual property and maintain compliance for your organization, you can use streaming to keep copies of your audit log data and monitor:
|
||||
{% data reusables.audit_log.audited-data-list %}
|
||||
|
||||
The benefits of streaming audit data include:
|
||||
To help protect your intellectual property and maintain compliance for your company, you can use streaming to keep copies of your audit log data. The audit log details events such as changes to settings and access, user membership, app permissions, and more. If you stream audit log data, you can take advantage of the following benefits.
|
||||
|
||||
- **Data exploration**. You can examine streamed events using your preferred tool for querying large quantities of data. The stream contains both audit events and Git events across the entire enterprise account.{% ifversion pause-audit-log-stream %}
|
||||
- **Data continuity**. You can pause the stream for up to seven days without losing any audit data.{% endif %}
|
||||
@@ -52,6 +49,14 @@ Enabling audit log streaming can cause a minor impact on the performance of {% d
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Events that appear in audit log streams
|
||||
|
||||
You can review the specific events that appear in streamed audit logs. For more information, see the following articles.
|
||||
|
||||
- "[AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)"
|
||||
- "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/audit-log-events-for-your-organization)"
|
||||
- "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/security-log-events)"
|
||||
|
||||
## Setting up audit log streaming
|
||||
|
||||
You set up the audit log stream on {% data variables.product.product_name %} by following the instructions for your provider.
|
||||
|
||||
@@ -17,14 +17,17 @@ topics:
|
||||
|
||||
## Using the audit log API
|
||||
|
||||
You can interact with the audit log using the REST API.{% ifversion read-audit-scope %} You can use the `read:audit_log` scope to access the audit log via the API.{% endif %}
|
||||
You can maintain compliance for your enterprise and secure your intellectual property by interacting with the audit log using the REST API. For more information about the specific events that you can access via the audit log API, see the following articles.
|
||||
|
||||
- "[AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/audit-log-events-for-your-enterprise)"
|
||||
- "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/audit-log-events-for-your-organization)"
|
||||
- "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/security-log-events)"
|
||||
|
||||
{% data reusables.audit_log.retention-periods %}
|
||||
|
||||
Timestamps and date fields in the API response are measured in [UTC epoch milliseconds](https://en.wikipedia.org/wiki/Unix_time).
|
||||
|
||||
To ensure your intellectual property is secure, and you maintain compliance for your enterprise, you can use the audit log REST API to keep copies of your audit log data and monitor:
|
||||
{% data reusables.audit_log.audited-data-list %}
|
||||
|
||||
{% data reusables.audit_log.retention-periods %}
|
||||
{% ifversion read-audit-scope %}You can use the `read:audit_log` scope to access the audit log via the API.{% endif %}
|
||||
|
||||
{% ifversion ghec %}Each audit log API endpoint has a rate limit of 1,750 queries per hour for a given combination of user and IP address. To avoid rate limiting, integrations that query the audit log API should query at a maximum frequency of 1,750 queries per hour. Additionally, if your integration receives a rate limit error (typically a 403 or 429 response), it should wait before making another request to the API. For more information, see "[AUTOTITLE](/rest/overview/rate-limits-for-the-rest-api)" and "[AUTOTITLE](/rest/guides/best-practices-for-integrators)."{% endif %}
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Increasing CPU or memory resources
|
||||
intro: 'You can increase the CPU or memory resources for a {% data variables.product.prodname_ghe_server %} instance.'
|
||||
intro: 'You can increase the CPU or memory resources for the virtual machine (VM) that runs {% data variables.location.product_location %}.'
|
||||
redirect_from:
|
||||
- /enterprise/admin/installation/increasing-cpu-or-memory-resources
|
||||
- /enterprise/admin/enterprise-management/increasing-cpu-or-memory-resources
|
||||
@@ -15,21 +15,24 @@ topics:
|
||||
- Performance
|
||||
shortTitle: Increase CPU or memory
|
||||
---
|
||||
|
||||
## About increasing CPU or memory resources
|
||||
|
||||
You can accommodate more resource-intensive workloads on {% data variables.location.product_location %} by increasing the VM's CPU or memory resources.
|
||||
|
||||
{% data reusables.enterprise_installation.warning-on-upgrading-physical-resources %}
|
||||
|
||||
{% note %}
|
||||
{% data reusables.enterprise_installation.warning-on-scaling %}
|
||||
|
||||
**Note:** Before increasing CPU or memory resources, put your instance in maintenance mode.{% ifversion ip-exception-list %} You can validate changes by configuring an IP exception list to allow access from specified IP addresses. {% endif %} For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)."
|
||||
## Adding CPU or memory resources on AWS
|
||||
|
||||
{% endnote %}
|
||||
To add CPU or memory resources for an instance on AWS, you must change the instance's type. You must have access to your company's AWS infrastructure, and you must be familiar with using either the AWS management console or the `aws ec2` command-line interface to manage EC2 instances. For more information, see [Change the instance type](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html) in the AWS documentation.
|
||||
|
||||
## Adding CPU or memory resources for AWS
|
||||
You can review resizing considerations, see supported instance types, and learn how to resize an instance on AWS.
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** To add CPU or memory resources for AWS, you must be familiar with using either the AWS management console or the `aws ec2` command line interface to manage EC2 instances. For background and details on using the AWS tools of your choice to perform the resize, see the AWS documentation on [resizing an Amazon EBS-backed instance](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html).
|
||||
|
||||
{% endnote %}
|
||||
- [Resizing considerations for AWS](/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources#resizing-considerations-for-aws)
|
||||
- [Supported instance types on AWS](/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources#supported-aws-instance-types)
|
||||
- [Resizing an instance on AWS](/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources#resizing-an-instance-on-aws)
|
||||
|
||||
### Resizing considerations for AWS
|
||||
|
||||
@@ -38,36 +41,35 @@ Before increasing CPU or memory resources for {% data variables.location.product
|
||||
- **Scale your memory with CPUs**. {% data reusables.enterprise_installation.increasing-cpus-req %}
|
||||
- **Assign an Elastic IP address to the instance**. If you haven't assigned an Elastic IP to your instance, you'll have to adjust the DNS A records for your {% data variables.product.prodname_ghe_server %} host after the restart to account for the change in public IP address. Once your instance restarts, the instance keeps the Elastic IP if you launched the instance in a virtual private cloud (VPC). If you create the instance in an EC2-Classic network, you must manually reassign the Elastic IP to the instance.
|
||||
|
||||
### Supported AWS instance types
|
||||
### Supported instance types on AWS
|
||||
|
||||
You need to determine the instance type you would like to upgrade to based on CPU/memory specifications.
|
||||
|
||||
{% data reusables.enterprise_installation.warning-on-scaling %}
|
||||
{% data reusables.enterprise_installation.increase-resources-view-specifications %}
|
||||
|
||||
{% data reusables.enterprise_installation.aws-instance-recommendation %}
|
||||
|
||||
### Resizing for AWS
|
||||
### Resizing an instance on AWS
|
||||
|
||||
{% note %}
|
||||
To increase the resources available to a {% data variables.product.prodname_ghe_server %} instance on AWS, you must shut down the instance, change the instance's type, then restart the instance.
|
||||
|
||||
**Note:** For instances launched in EC2-Classic, write down both the Elastic IP address associated with the instance and the instance's ID. Once you restart the instance, re-associate the Elastic IP address.
|
||||
|
||||
{% endnote %}
|
||||
|
||||
It's not possible to add CPU or memory resources to an existing AWS/EC2 instance. Instead, you must:
|
||||
|
||||
1. Stop the instance.
|
||||
1. Change the instance type.
|
||||
1. If your instances runs in EC2-Classic, note both the Elastic IP address associated with the instance and the instance's ID.
|
||||
{% data reusables.enterprise_installation.increase-resources-communicate-and-enable-maintenance-mode %}
|
||||
{% data reusables.enterprise_installation.increase-resources-shut-down %}
|
||||
1. On AWS, change the instance type.
|
||||
1. Start the instance.
|
||||
1. If your instance runs in EC2-Classic, after you restart the instance, re-associate the Elastic IP address.
|
||||
{% data reusables.enterprise_installation.configuration-recognized %}
|
||||
{% data reusables.enterprise_installation.increase-resources-test-in-maintenance-mode %}
|
||||
{% data reusables.enterprise_installation.increase-resources-disable-message-and-maintenance-mode %}
|
||||
|
||||
## Adding CPU or memory resources on Microsoft Azure
|
||||
|
||||
{% note %}
|
||||
To add CPU or memory resources for an instance on Microsoft Azure, you must change the instance's size. You must have access to your company's Microsoft Azure infrastructure, and you must be familiar with the Azure Portal, Azure CLI, or Azure PowerShell to manage Azure instances. For more information, see [Change the size of a virtual machine](https://learn.microsoft.com/en-us/azure/virtual-machines/resize-vm?tabs=portal) in the Azure documentation.
|
||||
|
||||
**Note:** To add CPU or memory resources in Microsoft Azure, you must be familiar with using either the Azure Portal, Azure CLI or Azure PowerShell to manage VM instances. For background and details on using the Azure tools of your choice to perform the resize, please refer to the Azure documentation on [changing the size of a virtual machine](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm).
|
||||
You can review resizing considerations, see supported instance types, and learn how to resize an instance on Microsoft Azure.
|
||||
|
||||
{% endnote %}
|
||||
- [Resizing considerations for Microsoft Azure](/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources#resizing-considerations-for-microsoft-azure)
|
||||
- [Supported instance types on Microsoft Azure](/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources#supported-instance-types-on-microsoft-azure)
|
||||
- [Resizing an instance on Microsoft Azure](/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources#resizing-an-instance-on-microsoft-azure)
|
||||
|
||||
### Resizing considerations for Microsoft Azure
|
||||
|
||||
@@ -76,36 +78,48 @@ Before increasing CPU or memory resources for {% data variables.location.product
|
||||
- **Scale your memory with CPUs**. {% data reusables.enterprise_installation.increasing-cpus-req %}
|
||||
- **Assign a static IP address to the instance**. If you haven't assigned a static IP to your instance, you might have to adjust the DNS A records for your {% data variables.product.prodname_ghe_server %} host after the restart to account for the change in IP address.
|
||||
|
||||
### Supported Microsoft Azure instance sizes
|
||||
### Supported instance types on Microsoft Azure
|
||||
|
||||
You need to determine the instance size you would like to upgrade to based on CPU/memory specifications.
|
||||
|
||||
{% data reusables.enterprise_installation.warning-on-scaling %}
|
||||
{% data reusables.enterprise_installation.increase-resources-view-specifications %}
|
||||
|
||||
{% data reusables.enterprise_installation.azure-instance-recommendation %}
|
||||
|
||||
### Resizing for Microsoft Azure
|
||||
### Resizing an instance on Microsoft Azure
|
||||
|
||||
You can scale the VM up by changing the VM size. Changing its size will cause it to be restarted. In some cases, you must deallocate the VM first. This can happen if the new size is not available on the hardware cluster that is currently hosting the VM.
|
||||
To increase the resources available to a {% data variables.product.prodname_ghe_server %} instance on Microsoft Azure, you must change the VM's size. Changing the VM's size will cause the VM to restart. In some cases, you must deallocate the VM first. You may need to deallocate the VM if the new size is not available on the hardware cluster that is currently hosting the VM.
|
||||
|
||||
1. Refer to the Azure documentation on [changing the size of a virtual machine](https://docs.microsoft.com/en-us/azure/virtual-machines/resize-vm) for the required steps.
|
||||
{% data reusables.enterprise_installation.increase-resources-communicate-and-enable-maintenance-mode %}
|
||||
{% data reusables.enterprise_installation.increase-resources-shut-down %}
|
||||
1. On Azure, to resize the VM, follow the instructions in [Change the size of a virtual machine](https://learn.microsoft.com/en-us/azure/virtual-machines/resize-vm?tabs=portal) in the Azure documentation.
|
||||
{% data reusables.enterprise_installation.configuration-recognized %}
|
||||
{% data reusables.enterprise_installation.increase-resources-test-in-maintenance-mode %}
|
||||
{% data reusables.enterprise_installation.increase-resources-disable-message-and-maintenance-mode %}
|
||||
|
||||
## Adding CPU or memory resources for OpenStack KVM
|
||||
|
||||
It's not possible to add CPU or memory resources to an existing OpenStack KVM instance. Instead, you must:
|
||||
|
||||
1. Take a snapshot of the current instance.
|
||||
1. Stop the instance.
|
||||
1. Select a new instance flavor that has the desired CPU and/or memory resources.
|
||||
|
||||
## Adding CPU or memory resources for VMware
|
||||
To increase the resources available to a {% data variables.product.prodname_ghe_server %} instance on OpenStack KVM, you must have access to your company's OpenStack KVM infrastructure, and you must stop the VM and then select a new instance flavor.
|
||||
|
||||
{% data reusables.enterprise_installation.increasing-cpus-req %}
|
||||
|
||||
1. Use the vSphere Client to connect to the VMware ESXi host.
|
||||
1. Shut down {% data variables.location.product_location %}.
|
||||
1. Select the virtual machine and click **Edit Settings**.
|
||||
1. Under "Hardware", adjust the CPU and/or memory resources allocated to the virtual machine as needed.
|
||||
1. Using OpenStack KVM, take a snapshot of the current instance.
|
||||
{% data reusables.enterprise_installation.increase-resources-communicate-and-enable-maintenance-mode %}
|
||||
{% data reusables.enterprise_installation.increase-resources-shut-down %}
|
||||
1. On OpenStack KVM, select a new instance flavor that has the desired CPU or memory resources.
|
||||
{% data reusables.enterprise_installation.configuration-recognized %}
|
||||
{% data reusables.enterprise_installation.increase-resources-test-in-maintenance-mode %}
|
||||
{% data reusables.enterprise_installation.increase-resources-disable-message-and-maintenance-mode %}
|
||||
|
||||
## Adding CPU or memory resources for VMware ESXi
|
||||
|
||||
To increase the resources available to a {% data variables.product.prodname_ghe_server %} instance on VMware, you must have access to your company's VMware infrastructure, and you must stop the VM and then adjust the resources in VMWare ESXi.
|
||||
|
||||
{% data reusables.enterprise_installation.increasing-cpus-req %}
|
||||
|
||||
{% data reusables.enterprise_installation.increase-resources-communicate-and-enable-maintenance-mode %}
|
||||
{% data reusables.enterprise_installation.increase-resources-shut-down %}
|
||||
1. To the VM's settings on the VMware ESXi host using the vSphere Client, select the VM, then click **Edit Settings**.
|
||||
1. Under "Hardware", adjust the CPU or memory resources allocated to the VM.
|
||||
1. To start the virtual machine, click **OK**.
|
||||
{% data reusables.enterprise_installation.configuration-recognized %}
|
||||
{% data reusables.enterprise_installation.increase-resources-test-in-maintenance-mode %}
|
||||
{% data reusables.enterprise_installation.increase-resources-disable-message-and-maintenance-mode %}
|
||||
|
||||
@@ -84,6 +84,14 @@ If you need to use multiple accounts on {% data variables.location.product_locat
|
||||
|
||||
{% endif %}
|
||||
|
||||
### Session cookies
|
||||
|
||||
{% data variables.product.company_short %} uses cookies to provide services and secure {% data variables.location.product_location %}. {% ifversion fpt or ghec %}You can review details about {% data variables.product.company_short %}'s cookies in the [privacy/cookies repository](https://github.com/privacy/cookies).{% endif %}
|
||||
|
||||
- The gist.{% ifversion fpt or ghec %}github.com{% elsif ghes %}HOSTNAME domain{% endif %} and {% ifversion fpt or ghec %}github.com domains{% elsif ghes %}base domain for your instance{% endif %} use separate cookies.
|
||||
- {% data variables.product.product_name %} typically marks a user session for deletion after two weeks of inactivity.
|
||||
- {% data variables.product.product_name %} does not immediately delete a session when you sign out. Periodically, {% data variables.product.product_name %} automatically deletes expired sessions.
|
||||
|
||||
## Authenticating with {% data variables.product.prodname_desktop %}
|
||||
|
||||
You can authenticate with {% data variables.product.prodname_desktop %} using your browser. For more information, see "[AUTOTITLE](/desktop/installing-and-authenticating-to-github-desktop/authenticating-to-github-in-github-desktop)."
|
||||
|
||||
@@ -29,3 +29,7 @@ You can view a list of devices that have logged into your account, and revoke an
|
||||
{% endnote %}
|
||||
|
||||
{% endif %}
|
||||
|
||||
## Further information
|
||||
|
||||
- "[AUTOTITLE](/authentication/keeping-your-account-and-data-secure/about-authentication-to-github#session-cookies)"
|
||||
|
||||
@@ -186,8 +186,7 @@ For example, you can make a GraphQL request to see all the new organization memb
|
||||
|
||||
### Using the REST API
|
||||
|
||||
To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log REST API to keep copies of your audit log data and monitor:
|
||||
{% data reusables.audit_log.audited-data-list %}
|
||||
To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log REST API to keep copies of your audit log data. For more information about the specific events you can access using the REST API, see "[AUTOTITLE](/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/audit-log-events-for-your-organization)."
|
||||
|
||||
{% data reusables.audit_log.audit-log-git-events-retention %}
|
||||
|
||||
|
||||
@@ -1,2 +0,0 @@
|
||||
{% data reusables.audit_log.audit-log-api-info %}{% ifversion git-events-audit-log %}
|
||||
- Git events, such as cloning, fetching, and pushing {% ifversion enable-git-events %}(must be enabled, see "[AUTOTITLE](/admin/monitoring-activity-in-your-enterprise/reviewing-audit-logs-for-your-enterprise/configuring-the-audit-log-for-your-enterprise)"){% endif %}{% endif %}
|
||||
@@ -1,6 +1,5 @@
|
||||
1. Once the instance has fully restarted and you can reach it, use the SSH administrative shell to verify that the new resource configuration is recognized:
|
||||
1. After the instance has fully restarted and you can reach it, verify that the new resource configuration is recognized. SSH into the instance, then run the following command.
|
||||
|
||||
```shell
|
||||
ssh -p 122 admin@HOSTNAME
|
||||
ghe-system-info
|
||||
```
|
||||
```shell
|
||||
ghe-system-info
|
||||
```
|
||||
|
||||
@@ -0,0 +1,4 @@
|
||||
1. Communicate the upcoming downtime to your users and enable maintenance mode. For more information, see the following articles.
|
||||
|
||||
- "[AUTOTITLE](/admin/managing-accounts-and-repositories/communicating-information-to-users-in-your-enterprise/customizing-user-messages-for-your-enterprise#creating-a-mandatory-message)"
|
||||
- "[AUTOTITLE](/admin/administering-your-instance/configuring-maintenance-mode/enabling-and-scheduling-maintenance-mode)"
|
||||
@@ -0,0 +1,2 @@
|
||||
1. If you configured a user message, remove the message.
|
||||
1. Disable maintenance mode.
|
||||
@@ -0,0 +1,5 @@
|
||||
1. To stop the instance, SSH into the instance, then run the following command. For more information, see "[AUTOTITLE](/admin/administering-your-instance/administering-your-instance-from-the-command-line/accessing-the-administrative-shell-ssh)."
|
||||
|
||||
```shell
|
||||
sudo poweroff
|
||||
```
|
||||
@@ -0,0 +1,3 @@
|
||||
{%- ifversion ip-exception-list %}
|
||||
1. Optionally, you can validate the changes by configuring an IP exception list to allow access from specified IP addresses. For more information, see "[AUTOTITLE](/admin/administering-your-instance/configuring-maintenance-mode/enabling-and-scheduling-maintenance-mode#validating-changes-in-maintenance-mode-using-the-ip-exception-list)."
|
||||
{%- endif %}
|
||||
@@ -0,0 +1 @@
|
||||
You need to determine the instance type you would like to upgrade to based on the CPU and memory specifications.
|
||||
@@ -1 +1 @@
|
||||
When you increase CPU resources, we recommend adding at least 6.5 GB of memory for each vCPU (up to 16 vCPUs) that you provision for the instance. When you use more than 16 vCPUs, you don't need to add 6.5 GB of memory for each vCPU, but you should monitor your instance to ensure it has enough memory.
|
||||
When you increase CPU resources, {% data variables.product.company_short %} recommends adding at least 6.5 GB of memory for each vCPU (up to 16 vCPUs) that you provision for the instance. When you use more than 16 vCPUs, you don't need to add 6.5 GB of memory for each vCPU, but you should monitor your instance to ensure it has enough memory.
|
||||
|
||||
@@ -1,5 +1 @@
|
||||
{% warning %}
|
||||
|
||||
**Note:** You can always scale up your CPU or memory by resizing your instance. However, because resizing your CPU or memory requires downtime for your users, we recommend over-provisioning resources to account for scale.
|
||||
|
||||
{% endwarning %}
|
||||
You can always scale up your CPU or memory by resizing your instance. Changing the resources available to your instance requires downtime for your users, so {% data variables.product.company_short %} recommends over-provisioning resources to account for scale.
|
||||
|
||||
@@ -1,5 +1 @@
|
||||
{% warning %}
|
||||
|
||||
**Warning:** The process for allocating new system resources varies by virtualization platform and resource type. You should always configure the monitoring and alerting of key system resources. For more information, see "[AUTOTITLE](/admin/enterprise-management/monitoring-your-appliance)."
|
||||
|
||||
{% endwarning %}
|
||||
The process for allocating new system resources varies by virtualization platform and resource type. You should always configure the monitoring and alerting of key system resources. For more information, see "[AUTOTITLE](/admin/enterprise-management/monitoring-your-appliance)."
|
||||
|
||||
Reference in New Issue
Block a user