This was very useful in refreshing my memory on how to do this. Most everything worked as it did for you, but there was one exception. In the step where you added a second line to your HelloWorld file and then committed and pushed it again, I see that your eclipse went right to the screen where you choose master and then add spec. Mine makes me copy/paste the github URL for my repo every time. Any idea why mine doesn't remember that URL like yours does?... The push still appears to work, it just means I have to do more copy/pasting to get there. Especially since I can't seem to get it to work with my password, so I had to create a personal access token, which is another thing I have to copy/paste each time. I feel like there were a lot less steps when I worked with Eclipse and GitHub for a group project a few years back! Maybe I just told it to remember my login creds back then.
I spent like two hours figuring out why git in Eclipse is not showing changed files in staging until I realized one has to save the project in Eclipse for the changes to appear. In some other IDEs I use projects are saved automatically so it was hard to figure this out
This is the best video on the topic. However, remote access to GitHub repositories using passwords has been disabled in Aug., 2021. Now, the remote access can be done using PAT's (Personal Access Tokens). I am providing the relevant link. ruclips.net/video/keRhfR9-m7Q/видео.html
Thank you for the tutorial, but why click master? Why not HEAD? What is the difference? I specified master as directed but my GitLab repository has main as the top branch. I tried to then push my project to main instead but now I just get rejected non-fast-forward errors.
HEAD refers to the branch that is currently checked out; master is the (older?) default for git/github/gitlab. Github changed the default sometime ago to "main" and gitlab did similar for v14.0 (docs.gitlab.com/ee/user/project/repository/branches/default.html). You must be using gitlab 14.0 or newer and so the default is "main" and you'll need to adjust if you're using eclipse: stackoverflow.com/questions/67333081/push-to-main-instead-of-master-from-eclipse-to-git
First of all thank you for this tutorial, I was looking for exactly this :) Unfortunately I am not a native speaker, and I am not too familiar with git commands so far, so for me it was confusing that which git command is equivalent to "Add to index" option. Could you please write it down? Thank you Chris :)
To add an individual file to the index for staging use git add (git-scm.com/docs/git-add): git add fileName To add all changed files in one command you can use git add --all
Incredibly helpful! Thank you.
it is a great tutorial for the real developer like me.
I selected the project, clicked on "Commit..." but nothing is added to the index ! And I can't click on push.
This was very useful in refreshing my memory on how to do this. Most everything worked as it did for you, but there was one exception. In the step where you added a second line to your HelloWorld file and then committed and pushed it again, I see that your eclipse went right to the screen where you choose master and then add spec. Mine makes me copy/paste the github URL for my repo every time. Any idea why mine doesn't remember that URL like yours does?...
The push still appears to work, it just means I have to do more copy/pasting to get there. Especially since I can't seem to get it to work with my password, so I had to create a personal access token, which is another thing I have to copy/paste each time. I feel like there were a lot less steps when I worked with Eclipse and GitHub for a group project a few years back! Maybe I just told it to remember my login creds back then.
Thanks.it's very helpful to me.
Nice tutorial. Thank you!
Nice vid, helped a lot, big thanks!
I spent like two hours figuring out why git in Eclipse is not showing changed files in staging until I realized one has to save the project in Eclipse for the changes to appear. In some other IDEs I use projects are saved automatically so it was hard to figure this out
Thanks for the video 🙏
thanks for your video you help mee today
This is the best video on the topic. However, remote access to GitHub repositories using passwords has been disabled in Aug., 2021. Now, the remote access can be done using PAT's (Personal Access Tokens). I am providing the relevant link.
ruclips.net/video/keRhfR9-m7Q/видео.html
Thank you for the tutorial, but why click master? Why not HEAD? What is the difference? I specified master as directed but my GitLab repository has main as the top branch. I tried to then push my project to main instead but now I just get rejected non-fast-forward errors.
HEAD refers to the branch that is currently checked out; master is the (older?) default for git/github/gitlab. Github changed the default sometime ago to "main" and gitlab did similar for v14.0 (docs.gitlab.com/ee/user/project/repository/branches/default.html). You must be using gitlab 14.0 or newer and so the default is "main" and you'll need to adjust if you're using eclipse: stackoverflow.com/questions/67333081/push-to-main-instead-of-master-from-eclipse-to-git
@@ChrisBourkeUNL Thank you very much. It is very kind of you to answer and so quickly.
i don't find the hello world folder in my system
First of all thank you for this tutorial, I was looking for exactly this :) Unfortunately I am not a native speaker, and I am not too familiar with git commands so far, so for me it was confusing that which git command is equivalent to "Add to index" option. Could you please write it down? Thank you Chris :)
To add an individual file to the index for staging use git add (git-scm.com/docs/git-add):
git add fileName
To add all changed files in one command you can use
git add --all
If you want to learn how to get started using command line git, I do it for my CS1 course using the CS50 IDE: ruclips.net/video/nxX8AWnaU9o/видео.html