Skip to main content

112 Search results for "ssh"

Get started / Getting started with Git /

Caching your GitHub credentials in Git

repositories using SSH, then you can authenticate using an SSH key instead of using other credentials. For information about setting up an SSH connection, see

Authentication / Account security /

Preventing unauthorized access

GitHub requires a password to perform sensitive actions, such as adding new SSH keys, authorizing applications, or modifying team members. After changing

Codespaces / Troubleshooting /

Troubleshooting authentication to a repository

to the remote repository. For example, you may have configured Git to use SSH by including lines like the following in a config file in your dotfiles. [url

Authentication /

Keeping your account and data secure

GitHub credentials include not only your password, but also the access tokens, SSH keys, and application API tokens you use to communicate with GitHub. Should

Pull requests / Collaborate with pull requests / Working with forks /

Fork a repository

clone the repository using an SSH key, including a certificate issued by your organization's SSH certificate authority, click SSH, then click . To clone a repository

Codespaces / Developing in a codespace /

Using GitHub Codespaces in your JetBrains IDE

cores. The codespace must also be running an SSH server. For more information, see "Codespace running an SSH server." JetBrains license You must

Codespaces / Setting your user preferences /

Setting your default editor for GitHub Codespaces

application, you must have an SSH server running on the codespace. The codespace you connect to must be running an SSH server. The default dev container

Authentication / Account security /

Managing your personal access tokens

HTTPS Git operations. If your repository uses an SSH remote URL, you will need to switch the remote from SSH to HTTPS. If you are not prompted for your username

Authentication / Verify commit signatures /

Displaying verification statuses for all of your commits

commits and tags are marked "Verified" if they are signed with a GPG, SSH, or S/MIME key that was successfully verified. If a commit or tag has a signature

GitHub Desktop / Install & authenticate /

Authenticating to GitHub in GitHub Desktop

that you do not have a valid SSH key set up. To troubleshoot, see "Generating a new SSH key and adding it to the ssh-agent." Failed to clone fatal: