Remove deprecated GHES versions from content and data (#15830)
* ran script/remove-unused-assets.js (manually removed unused variables printed by the script) * package-lock * turn elsif into two ifs to prepare for running Liquid deprecation script * ran script/remove-deprecated-enterprise-version-markup.js --release 2.14 (ONLY UPDATES LINE BREAKS ETC.) * ran script/remove-deprecated-enterprise-version-markup.js --release 2.15 * ran script/remove-deprecated-enterprise-version-markup.js --release 2.17 * ran script/remove-deprecated-enterprise-version-markup.js --release 2.18 * update hardcoded test * Update content/github/collaborating-with-issues-and-pull-requests/filtering-files-in-a-pull-request.md Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> * add currentVersion is NOT free-pro-team to conditional, to make sure the deprecation script does the right thing when it is time to deprecate 2.21 Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com>
This commit is contained in:
@@ -16,7 +16,6 @@ You can access your resources in {% data variables.product.product_name %} in a
|
||||
- Personal access token
|
||||
- SSH key
|
||||
|
||||
|
||||
### Authenticating in your browser
|
||||
|
||||
You can authenticate to {% data variables.product.product_name %} in your browser in different ways.
|
||||
|
||||
@@ -18,9 +18,7 @@ We recommend that you regularly [review your SSH keys list](/articles/reviewing-
|
||||
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 currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}
|
||||
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 {% data variables.product.product_name %} account. For more information, see "[About SSH certificate authorities](/articles/about-ssh-certificate-authorities)."
|
||||
{% endif %}
|
||||
|
||||
### Further reading
|
||||
|
||||
|
||||
@@ -20,8 +20,7 @@ versions:
|
||||
3. Check the directory listing to see if you already have a public SSH key. By default, the filenames of the public keys are one of the following:
|
||||
- *id_rsa.pub*
|
||||
- *id_ecdsa.pub*
|
||||
- *id_ed25519.pub*{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %}
|
||||
- *id_dsa.pub*{% endif %}
|
||||
- *id_ed25519.pub*
|
||||
|
||||
If you don't have an existing public and private key pair, or don't wish to use any that are available to connect to {% data variables.product.product_name %}, then [generate a new SSH key](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent).
|
||||
|
||||
|
||||
@@ -86,29 +86,17 @@ On most devices and browsers, you can use a physical security key over USB or NF
|
||||
Authentication with a security key is *secondary* to authentication with a TOTP application{% if currentVersion == "free-pro-team@latest" %} or a text message{% endif %}. If you lose your security key, you'll still be able to use your phone's code to sign in.
|
||||
|
||||
1. You must have already configured 2FA via a TOTP mobile app{% if currentVersion == "free-pro-team@latest" %} or via SMS{% endif %}.
|
||||
2. Ensure that you have a {% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}WebAuthn{% else %}FIDO U2F{% endif %} compatible security key inserted into your computer.
|
||||
2. Ensure that you have a WebAuthn compatible security key inserted into your computer.
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{% data reusables.user_settings.security %}
|
||||
5. Next to "Security keys", click **Add**.
|
||||

|
||||
6. Under "Security keys", click **Register new security key**.
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}
|
||||

|
||||
{% else %}
|
||||

|
||||
{% endif %}
|
||||
7. Type a nickname for the security key, then click **Add**.
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}
|
||||

|
||||
{% else %}
|
||||

|
||||
{% endif %}
|
||||
8. Activate your security key, following your security key's documentation.
|
||||
{% if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.18" %}
|
||||

|
||||
{% else %}
|
||||

|
||||
{% endif %}
|
||||
9. Confirm that you've downloaded and can access your recovery codes. If you haven't already, or if you'd like to generate another set of codes, download your codes and save them in a safe place. If you lose access to your account, you can use your recovery codes to get back into your account. For more information, see "[Recovering your account if you lose your 2FA credentials](/articles/recovering-your-account-if-you-lose-your-2fa-credentials)."
|
||||

|
||||
{% data reusables.two_fa.test_2fa_immediately %}
|
||||
|
||||
@@ -119,7 +119,7 @@ The `ssh-add` command *should* print out a long string of numbers and letters. I
|
||||
|
||||
{% tip %}
|
||||
|
||||
**Tip**: On most systems the default private keys (`~/.ssh/id_rsa`{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %}, `~/.ssh/id_dsa`{% endif %} and `~/.ssh/identity`) are automatically added to the SSH authentication agent. You shouldn't need to run `ssh-add path/to/key` unless you override the file name when you generate a key.
|
||||
**Tip**: On most systems the default private keys (`~/.ssh/id_rsa` and `~/.ssh/identity`) are automatically added to the SSH authentication agent. You shouldn't need to run `ssh-add path/to/key` unless you override the file name when you generate a key.
|
||||
|
||||
{% endtip %}
|
||||
|
||||
|
||||
@@ -31,11 +31,7 @@ To avoid losing your password in the future, we suggest using a secure password
|
||||
|
||||
1. {% data variables.product.signin_link %} to {% data variables.product.product_name %}.
|
||||
{% data reusables.user_settings.access_settings %}
|
||||
{%- if currentVersion == "free-pro-team@latest" or currentVersion ver_gt "enterprise-server@2.17" %}
|
||||
{% data reusables.user_settings.security %}
|
||||
{%- else %}
|
||||
{% data reusables.user_settings.account_settings %}
|
||||
{%- endif %}
|
||||
4. Under "Change password", type your old password, a strong new password, and confirm your new password. For help creating a strong password, see "[Creating a strong password](/articles/creating-a-strong-password)"
|
||||
5. Click **Update password**.
|
||||
|
||||
|
||||
@@ -58,7 +58,7 @@ fi
|
||||
unset env
|
||||
```
|
||||
|
||||
If your private key is not stored in one of the default locations (like `~/.ssh/id_rsa`{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %} or `~/.ssh/id_dsa`{% endif %}), you'll need to tell your SSH authentication agent where to find it. To add your key to ssh-agent, type `ssh-add ~/path/to/my_key`. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/)"
|
||||
If your private key is not stored in one of the default locations (like `~/.ssh/id_rsa`), you'll need to tell your SSH authentication agent where to find it. To add your key to ssh-agent, type `ssh-add ~/path/to/my_key`. For more information, see "[Generating a new SSH key and adding it to the ssh-agent](/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/)"
|
||||
|
||||
{% tip %}
|
||||
|
||||
@@ -89,8 +89,7 @@ The `ssh-agent` process will continue to run until you log out, shut down your c
|
||||
|
||||
On OS X Leopard through OS X El Capitan, these default private key files are handled automatically:
|
||||
|
||||
- *.ssh/id_rsa*{% if currentVersion != "free-pro-team@latest" and currentVersion ver_lt "enterprise-server@2.19" %}
|
||||
- *.ssh/id_dsa*{% endif %}
|
||||
- *.ssh/id_rsa*
|
||||
- *.ssh/identity*
|
||||
|
||||
The first time you use your key, you will be prompted to enter your passphrase. If you choose to save the passphrase with your keychain, you won't have to enter it again.
|
||||
|
||||
Reference in New Issue
Block a user