Make images accessible in images/enterprise/ subdirectories Mi-Or (#34812)
Co-authored-by: Laura Coursen <lecoursen@github.com>
Joe Clark
|
Before Width: | Height: | Size: 91 KiB |
|
Before Width: | Height: | Size: 72 KiB |
|
Before Width: | Height: | Size: 61 KiB |
|
Before Width: | Height: | Size: 53 KiB |
|
Before Width: | Height: | Size: 2.8 KiB |
|
Before Width: | Height: | Size: 2.6 KiB |
|
Before Width: | Height: | Size: 3.0 KiB |
|
Before Width: | Height: | Size: 37 KiB |
|
Before Width: | Height: | Size: 27 KiB |
|
Before Width: | Height: | Size: 36 KiB |
|
Before Width: | Height: | Size: 6.4 KiB |
|
Before Width: | Height: | Size: 17 KiB After Width: | Height: | Size: 116 KiB |
|
Before Width: | Height: | Size: 8.1 KiB |
|
Before Width: | Height: | Size: 14 KiB |
|
Before Width: | Height: | Size: 15 KiB |
|
Before Width: | Height: | Size: 22 KiB |
|
Before Width: | Height: | Size: 28 KiB |
|
Before Width: | Height: | Size: 26 KiB |
|
Before Width: | Height: | Size: 12 KiB |
@@ -23,7 +23,5 @@ shortTitle: Set the IP using the console
|
||||
|
||||
{% data reusables.enterprise_installation.open-vm-console-start %}
|
||||
3. Choose to configure the `IPv4` or `IPv6` protocol.
|
||||
|
||||
4. Configure options for the protocol you chose.
|
||||
|
||||
{% data reusables.enterprise_installation.vm-console-done %}
|
||||
|
||||
@@ -50,12 +50,9 @@ To upgrade to the latest version of {% data variables.product.prodname_enterpris
|
||||
2. In a browser, navigate to the new replica appliance's IP address and upload your {% data variables.product.prodname_enterprise %} license.
|
||||
3. Set an admin password.
|
||||
5. Click **Migrate**.
|
||||
|
||||
6. Paste your backup host access SSH key into "Add new SSH key".
|
||||
|
||||
6. In the "Add new SSH key" text field, paste your backup host access SSH key.
|
||||
7. Click **Add key** and then click **Continue**.
|
||||
8. Copy the `ghe-restore` command that you'll run on the backup host to migrate data to the new instance.
|
||||
|
||||
9. Enable maintenance mode on the old instance and wait for all active processes to complete. For more information, see "[AUTOTITLE](/admin/configuration/configuring-your-enterprise/enabling-and-scheduling-maintenance-mode)."
|
||||
|
||||
{% note %}
|
||||
@@ -87,9 +84,7 @@ To upgrade to the latest version of {% data variables.product.prodname_enterpris
|
||||
```
|
||||
|
||||
12. Return to the new instance's restore status screen to see that the restore completed.
|
||||
|
||||
13. Click **Continue to settings** to review and adjust the configuration information and settings that were imported from the previous instance.
|
||||
|
||||
14. Click **Save settings**.
|
||||
|
||||
{% note %}
|
||||
|
||||
@@ -58,9 +58,7 @@ An organization administrator can only configure hook permissions for an organiz
|
||||
{% data reusables.profile.access_org %}
|
||||
{% data reusables.profile.org_settings %}
|
||||
4. In the left sidebar, click **Hooks**.
|
||||
|
||||
5. Next to the pre-receive hook that you want to configure, click the **Hook permissions** drop-down menu. Select whether to enable or disable the pre-receive hook, or allow it to be configured by the repository administrators.
|
||||
|
||||
5. Next to the pre-receive hook that you want to configure, select the **Hook permissions** dropdown menu, then click an option.
|
||||
|
||||
## Configure pre-receive hooks for a repository
|
||||
|
||||
|
||||
@@ -57,8 +57,7 @@ You must be a site admin and an organization owner to create a team with LDAP sy
|
||||
{% data reusables.user-settings.access_org %}
|
||||
{% data reusables.organizations.new_team %}
|
||||
{% data reusables.organizations.team_name %}
|
||||
6. Search for an LDAP group's DN to map the team to. If you don't know the DN, type the LDAP group's name. {% data variables.product.prodname_ghe_server %} will search for and autocomplete any matches.
|
||||
|
||||
6. Under "LDAP group", search for an LDAP group's DN to map the team to. If you don't know the DN, type the LDAP group's name. {% data variables.product.prodname_ghe_server %} will search for and autocomplete any matches.
|
||||
{% data reusables.organizations.team_description %}
|
||||
{% data reusables.organizations.team_visibility %}
|
||||
{% data reusables.organizations.create-team-choose-parent %}
|
||||
|
||||
@@ -19,23 +19,11 @@ shortTitle: Project management with Jira
|
||||
---
|
||||
## Connecting Jira to a {% data variables.product.prodname_enterprise %} organization
|
||||
|
||||
1. Sign into your {% data variables.product.prodname_enterprise %} account at http[s]://[hostname]/login. If already signed in, click on the {% data variables.product.prodname_dotcom %} logo in the top left corner.
|
||||
1. Sign into your {% data variables.product.prodname_enterprise %} account at `http[s]://[hostname]/login`. If already signed in, click on the {% data variables.product.prodname_dotcom %} logo in the top left corner.
|
||||
2. Click on your profile icon under the {% data variables.product.prodname_dotcom %} logo and select the organization you would like to connect with Jira.
|
||||
|
||||
|
||||
|
||||
3. Click on the **Edit _organization name_ settings** link.
|
||||
|
||||
|
||||
|
||||
4. In the left sidebar, under **Developer settings**, click **OAuth Apps**.
|
||||
|
||||
|
||||
|
||||
5. Click on the **Register new application** button.
|
||||
|
||||
|
||||
|
||||
6. Fill in the application settings:
|
||||
- In the **Application name** field, type "Jira" or any name you would like to use to identify the Jira instance.
|
||||
- In the **Homepage URL** field, type the full URL of your Jira instance.
|
||||
@@ -47,17 +35,8 @@ shortTitle: Project management with Jira
|
||||
|
||||
1. On your Jira instance, log into an account with administrative access.
|
||||
2. At the top of the page, click the settings (gear) icon and choose **Applications**.
|
||||
|
||||
|
||||
|
||||
3. In the left sidebar, under **Integrations**, click **DVCS accounts**.
|
||||
|
||||
|
||||
|
||||
4. Click **Link Bitbucket Cloud or {% data variables.product.prodname_dotcom %} account**.
|
||||
|
||||
|
||||
|
||||
5. In the **Add New Account** modal, fill in your {% data variables.product.prodname_enterprise %} settings:
|
||||
- From the **Host** dropdown menu, choose **{% data variables.product.prodname_enterprise %}**.
|
||||
- In the **Team or User Account** field, type the name of your {% data variables.product.prodname_enterprise %} organization or user account.
|
||||
|
||||
@@ -28,7 +28,9 @@ If your organization [requires members to use two-factor authentication](/organi
|
||||
{% data reusables.organizations.people %}
|
||||
{% data reusables.organizations.people_tab_outside_collaborators %}
|
||||
{% ifversion fpt or ghec %}
|
||||
5. To the right of the name of the outside collaborator you want to become a member, use the {% octicon "gear" aria-label="The gear icon" %} drop-down menu and click **Invite to organization**.
|
||||
5. To the right of the name of the outside collaborator you want to become a member, select the {% octicon "kebab-horizontal" aria-label="Collaborator settings" %} dropdown menu and click **Invite to organization**.
|
||||
|
||||
|
||||
{% else %}
|
||||
5. To the right of the name of the outside collaborator you want to become a member, click **Invite to organization**.
|
||||
{% endif %}
|
||||
|
||||
@@ -1,2 +1 @@
|
||||
1. In the upper-left corner of any page, click <span aria-label="the Octocat icon" class="octicon octicon-mark-github"></span>.
|
||||
|
||||
1. In the upper-left corner of any page, click {% octicon "mark-github" aria-label="Global navigation" %}.
|
||||
|
||||
@@ -1,3 +1,2 @@
|
||||
1. Using your virtualization platform tools, open the virtual machine console.
|
||||
|
||||
2. To start your network setup, press **S**.
|
||||
|
||||