May be the following links would help you. www.nobledesktop.com/learn/git/stage-commit-files#:~:text='%2C%20to%20stage%20a%20specific%20file,%2Dr%20%5Bfolderpath%5D'%20respectively. stackoverflow.com/questions/24167676/cant-stage-folder-for-commit-with-git-add-or-git-add-u
Thanks for the question. Actually, Personal access tokens (PAT) and SSH keys serve different purposes for authentication in GitHub. PATs are used for HTTPS authentication and act as a replacement for your GitHub password when performing Git operations or accessing the API. You enter the token when prompted for a username and password, and it can be included in the URL or stored in a credential manager. PATs allow for fine-grained access control, as you can set specific permissions for them. On the other hand, SSH keys are used for authenticating over SSH, providing a more secure and convenient method for tasks like cloning repositories, pushing, and pulling changes. After generating an SSH key pair, you add the public key to your GitHub account and can then use the SSH URL for Git operations without needing to enter a password. Overall, use PATs for HTTPS connections and SSH keys for SSH connections, with each offering different methods and security benefits. I hope this helps clarify the differences.😊
This was really helpful, thanks!
You are most welcome 😊
Thank you. New sub here from a fellow Sri Lankan.
Thanks a lot 😊
Nice work 💪
Awesome work thanu❤️
Nice informative video, really like it
Great one. Very informative 👍
Good job duwa 👍
Good job
very informative
This is an elegant feature btw. I got an issue: I can't even staged a file folder to commit in R project to git
May be the following links would help you.
www.nobledesktop.com/learn/git/stage-commit-files#:~:text='%2C%20to%20stage%20a%20specific%20file,%2Dr%20%5Bfolderpath%5D'%20respectively.
stackoverflow.com/questions/24167676/cant-stage-folder-for-commit-with-git-add-or-git-add-u
thanks a lot
You are most welcome 😀 and thanks a lot for watching the video
What's the difference between a personal token and an SSH key?
Thanks for the question. Actually, Personal access tokens (PAT) and SSH keys serve different purposes for authentication in GitHub. PATs are used for HTTPS authentication and act as a replacement for your GitHub password when performing Git operations or accessing the API. You enter the token when prompted for a username and password, and it can be included in the URL or stored in a credential manager. PATs allow for fine-grained access control, as you can set specific permissions for them. On the other hand, SSH keys are used for authenticating over SSH, providing a more secure and convenient method for tasks like cloning repositories, pushing, and pulling changes. After generating an SSH key pair, you add the public key to your GitHub account and can then use the SSH URL for Git operations without needing to enter a password. Overall, use PATs for HTTPS connections and SSH keys for SSH connections, with each offering different methods and security benefits. I hope this helps clarify the differences.😊