(491) GitHub Tutorial without using the Command Line

This is a replay of video 425 (During my summer break)
Today, working with GitHub is a fundamental skill. Most libraries and projects reside on GitHub, and we must know how to use them. GitHub can also enhance our work procedure, and a lot of employers will ask you for your GitHub account or will check it out before they invite you for an interview. So, GitHub seems at least as crucial as LinkedIn for a professional developer’s career.
This video will teach you the basics of using GitHub for your Arduino projects. And I promise: We will avoid the command line!

Links:

Patreon supporter companies:

The links above are usually affiliate links that support the channel (at no additional cost to you).
If you want to support the channel, please use the links below to start your shopping. No additional charges for you, but I get a commission on your purchases to buy new stuff for the channel

Please do not try to email me. This communication channel is reserved for my primary job
As an Amazon Associate, I earn from qualifying purchases
#no#midroll#ads

[martyb]

Very good video! I have seen github but never really understood it. Well done!

[stephang]

Hi Andreas I lost track of your videos, but loved this one. I have to work it through carefully later, but I think I will finally understand the basics of github...

[LORRY]

Nice Video.

Andreas, thank you very much for this highly informative contribution. I'm sure many hobbyists will benefit from it. Keep up the great work...

[langrock]

Thanks for this nice overview.

I think we should distinguish between 'git', the code-versioning software, and Github, the place a 'git' repository can be stored online. There are other online providers that offer the same service, for example Bitbucket; you can also run this on a local server. If you use 'git' to track your own code or other documents, there may not be a need to ever push the repository to an online server, or you may run a server locally within your network. For example, I used a local repository to track Latex files when writing articles or my dissertation. This turned out to be pretty useful for versioning.

In short, to those interested in creating repositories, it's really 'git' that you should look into, not so much Github; don't be afraid of the command line either, since there's really only a small subset of commands that are being used in 99% of all use cases. Most modern IDEs already have modules that make working on files in a repository pretty seamless, negating the need for tools like Github Desktop altogether.

[arp_catchall]

As usual.... Andreas... a very useful video. Thanks! I haven't used them, but now will. Great explanation.

[Rpol_]

Nice video Andreas. I work in Aerospace where we’ve used PVCS Version Manager and Tracker for decades. Once a project was setup, PVCS was infinitely more straightforward and easy to use than Git. However, to keep tools within our organization common and move to industry standards, we’ve recently moved to Git. The learning curve was difficult for me to say the least and I still struggle with missing features we had with PVCS. I only wish I had this video a couple of years ago!

[ellerycadel]

Finally a clear explanation!! Thank you.

[gabest]

If your goal is a pull request, first make a branch in the fork and modify that. Unless it's a one man show, no one accepts pull requests to the main branch.

[HarryCountry]

Vielen Dank Andres! Schoen langsam fange ich an zu verstehen wie Github funktioniert! 😁

[paulow.bungner]

great video Andreas. thank you. (Obrigado !)

[tubeDude]

I HATE Dropbox! Very good explanation! 👍

[peircedan]

I would suggest working with Git is a fundamental skill and that Github is convenient site to share Git repositories. The majority of Git tutorials make use of the command line and I think it is a good idea to use that approach. I would not expect a developer to be reluctant to use the command line.

[GeorgeGraves]

I know just enough git to be dangerous. Thanks for making this.

[jjsjeffjjsjeff]

What I don't understand is after you fork how do improvements made by the original project get included in my forked version of the project? Or once it's forked it's like a completely different project forever?

[youtou]

I'm not convinced, this ghitub thing will probably never get adopted

[pdrg]

Why "pull request" when you are asking to push to production?

[nicodesmidt]

Wouldn’t most pull request be initiated from an “issue” ?

[neerajbisht]

Sir I want to work with your esp32 cam . I hv an idea of a project smart street light and home automation togather.do this possible.if you are interested.

[Versette]

Welp, this video will certainly get many many views xd
I've talked to so many people who don't want to deal with the command line...

[TimoNoko]

Why the Command Line Github is so incomprehensible? It should update the files without whining about tokens and passwords and god-knows-what. Dont understand.