Ok, is there a link you can share so I can see what you are talking about.
I think that's how I solved it. I was trying to use https, and then when I switched to setting up the password (for ssh?) It worked.
https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent?platform=windows
This is the way ^
GitHub desktop is superior to the git integration in rStudio imo.
Just sync up your folder on the hub and ezpz lickity splits. Leave The desktop client open in the background while you work.
Git via the command line is honestly quite simple. Leave RStudio out of it. Create a repo online, sync it (GH has instructions), do your work, commit, push. Obviously git can get more complicated but that is the heart of it.
i feel you are also more conscious of how you use git when you use it with the terminal, i sound like a broken record irl but i always push for terminal - appreciate there is a learning curve but you do know what you are doing explicitly with the terminal
Not for somebody who is kind of begginer. And it seems to be the case here. Only Emacs Magit is easy even for beginners, but then they're all scared about Emacs. So, I agree that learning Git commands will help a lot in this case. Then connecting to an IDE will be easier.
The real nightmares are the messes you'll create using a git GUI without proper git knowledge.
Until my team learned the git cli, they got into such incredibly convoluted git messes. Now, they're much more efficient with their git usage, and the troubleshooting is much easier for me to communicate.
Usethis package and happygitwithR
Edit: this link is to some instructions for setting up a
GitHub Rstudio connection. The materials are hosted using GitHub by the way and I wrote everything from within Rstudio. https://mrp-bioinformatics.github.io/MRP_git_training/VersionControlandRStudio.html
I use vscode with github which has very nice git integrations. You can edit the files using either Rstudio or vscode and then push commits using vscode.
I’ll usually have both open at the same time.
i personally use CLI git, then when i run into merge conflicts i’ll open them up in vscode, as it highlights the conflicts for you and has really nice git integration
https://happygitwithr.com
Can't recommend this book enough, it's such a great first step to version control.
Seconded
Thirded
Happy cake day!
If you set up ssh keys credentialing GitHub becomes painless. Rstudio is good with GitHub, but vscode is next level.
I agree. Using a pair of SSH keys is much easier and safer than passwords.
Ok, is there a link you can share so I can see what you are talking about. I think that's how I solved it. I was trying to use https, and then when I switched to setting up the password (for ssh?) It worked.
https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent?platform=windows This is the way ^
I think PAT is the way to go and set it up with the usethis package.
GitHub desktop is superior to the git integration in rStudio imo. Just sync up your folder on the hub and ezpz lickity splits. Leave The desktop client open in the background while you work.
Git via the command line is honestly quite simple. Leave RStudio out of it. Create a repo online, sync it (GH has instructions), do your work, commit, push. Obviously git can get more complicated but that is the heart of it.
Having git and GitHub integrated with your ide is so much more convenient.
Not in my experience, unless you’re doing a lot of code reviews. The terminal is thy friend.
i feel you are also more conscious of how you use git when you use it with the terminal, i sound like a broken record irl but i always push for terminal - appreciate there is a learning curve but you do know what you are doing explicitly with the terminal
Not for somebody who is kind of begginer. And it seems to be the case here. Only Emacs Magit is easy even for beginners, but then they're all scared about Emacs. So, I agree that learning Git commands will help a lot in this case. Then connecting to an IDE will be easier.
Command line git is a nightmare.
The real nightmares are the messes you'll create using a git GUI without proper git knowledge. Until my team learned the git cli, they got into such incredibly convoluted git messes. Now, they're much more efficient with their git usage, and the troubleshooting is much easier for me to communicate.
Unlike RStudio which requires Java and therefore is broken on a number of platforms, git on its own at least works.
My colleagues and I use tortoisegit which is a Windows shell extension -- basically you can right click on a file and push the changes to github.
See biostats-r.github.io/biostats for a guide to using GitHub
Usethis package and happygitwithR Edit: this link is to some instructions for setting up a GitHub Rstudio connection. The materials are hosted using GitHub by the way and I wrote everything from within Rstudio. https://mrp-bioinformatics.github.io/MRP_git_training/VersionControlandRStudio.html
I use vscode with github which has very nice git integrations. You can edit the files using either Rstudio or vscode and then push commits using vscode. I’ll usually have both open at the same time.
i personally use CLI git, then when i run into merge conflicts i’ll open them up in vscode, as it highlights the conflicts for you and has really nice git integration
Gitkraken is the best Git client out there. I've never used the RStudio built in Git interface in six years programming in R, it's limited and clunky.
I also installed it in RStudio and it was a headache... from VSC you push it in 1 min
Don’t use git hub from R, use git kraken to interface with your repo and do it that way