109 Search results for "ssh"

Managing commit signature verification GitHub will verify GPG, SSH, or S/MIME signatures so other people will know that your commits come from a trusted

admin@HOSTNAME:/home/admin/ SSH into your target GitHub Enterprise Server instance. For more information, see Accessing the administrative shell (SSH). ssh -p 122 admin@HOSTNAME

As a security precaution, SSH keeps track of which hosts it has previously seen. This error means that the server to which you're connecting presented

credentials will cause authentication to fail. Use SSH instead If you've previously set up SSH keys, you can use the SSH clone URL instead of HTTPS. For more information

Stop a codespace Delete a codespace Rename a codespace Rebuild a codespace SSH into a codespace Open a codespace in Visual Studio Code Open a codespace in

Enterprise Server source. The best way to do this is to verify that you can SSH into the instance. Generate an access token with the repo and admin:org scopes

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

HTTPS remote URL has some advantages compared with using SSH. It's easier to set up than SSH, and usually works through strict firewalls and proxies. However

captcha verification. Switching cloning methods Switching from cloning via SSH to cloning via HTTPS, or vice versa may improve connectivity. For more information

remote repository URL. Tip For information on the difference between HTTPS and SSH URLs, see About remote repositories. The git remote set-url command takes