Видео

@@lite_anime thanks for the suggestion! I’ll add that to my list. 🙏 It shouldn’t be too different than the regular JS setup, but you’ll probably need the TypeScript plugin for ESLint.

@@Neosilvium27 Hope it helps!

I’ve always used the GitLens extension in the past, but it’s changed a lot over the years and they charge for the premium features. I see a lot of folks recommending GitGraph these days (also an extension). Hope that helps!

🏆 🏆 🏆

I'm confused. What does this mean? 😆

Happy to help!

Glad it was helpful! 😊

Formatting imports and using the plugins that helop do that. Great video btw

@olabanjoolakunori5151 I'm working on a video about prettier right now, and then I'll follow that one up with a video about using ESLint and Prettier together to do some auto formatting. Thanks for watching!

@@thecommoncoder That's superb, thank you🙏🏾

Good question! This video and the upload project video are loosely related, but are more or less independent topics. This video focuses more on the essential commands for working with GitHub, while the other video is more about taking an existing project on your computer and putting it up on GitHub. There is definitely some overlap though. 👍

@@christopherlyons7613 Great question! As long as your repositories are public, students will have read-only access to any code within the repository (even without an SSH key or a GitHub account). They can either clone the repo using HTTPS, the GitHub CLI, or by downloading the repo as a zip file. The SSH key becomes important when you are creating your own repositories, or you are a contributor to another repository and GitHub needs to know who you are. Hope that helps!

​@@thecommoncoderGreat thank you. So if I create a PUBLIC repository then anyone can download (CLONE) the repository regardless of SSH key status, correct? Now what happens if I create a PRIVATE repository? Which I'm leaning to since I'd rather restrict access just to my students (but I wouldn't want to have them create SSH keys and require me to add/delete all that for every class). This is where a userid/password seems to make more sense for my use case. Is there any way to configure it to work the way I want?

@christopherlyons7613 For a private repo, you'll have to grant each student access to the repo. Students would need to setup an SSH key for read-only access in that case, but that doesn't require anything to be done on your end. However, you will have to manually add the list of students to the repository though, which can be tedious depending on the number of students. For some additional context, SSH keys are computer/account specific. This means that each student would manage their own SSH key(s) for their GitHub Account. It essentially sets up the authentication between their computer and their GitHub account so you don't have to put in a username/password each time something on your computer interacts with GitHub (command line, VS Code, GitHub Desktop, etc).

@@thecommoncoder K. Is there any way to setup a PUBLIC repo that you can restrict who can gain access? Guess that doesn't really make sense but I think what I need to do will be easiest to handle with a PUBLIC repo but I'd like to limit that to just class students. I don't want to take them through SSH setup nor really require them to have a Git account to access the files. I could also just do this through a shared cloud drive. But I wanted to at least introduce them to Git & GitHub and thought this would be a way to do that.

@christopherlyons7613 Not that I'm aware of. I feel like you run the same risk either way with a public repo or a shared cloud drive link. That link could theoretically be shared with anyone just the same as a link to the repository. It think the best option in this case would be a public repo if you don't want to manage access.

Are you able to run "node -v" in the command line and see the version? If not, you might want to try re-installing and/or restarting your computer. If the above command works, how are you trying to run your JavaScript code? To run code in a JavaScript file, you'll need to type "node path/to/javascript/file.js" in the command line in order to run it. Usually, you'll want to navigate to the location of your project with the command line, and then run your project files from there. For example, if your project was in "~/Documents/Code/MyProject" and your JavaScript file was called "index.js", you'd want to first navigate to the project folder using "cd ~/Documents/Code/MyProject", then run "node index.js" whenever you wanted to run your code. Hope that helps!

@@thecommoncoder Thanks 😀

I can't run it I got a message saying to run the file in a shell now I try to run it and an error message came up. please help me

You're very welcome. Thanks for watching! 😊

Please do more, Really dense and practical delivery, thank you

@drivetrainerYT Thats the plan! Thanks for watching 🙏

That’s awesome! Glad it was helpful. 😊

I've got that in the queue!

In this context, “lightweight” just means that it’s not very resource intensive on your machine. Its main focus is on the code, but it can be customized and extended based on what types of projects that you are working on. Other editors offer a more “all in one” solution, but they are usually more resource intensive, take up more disk space, and are specific to a certain type of development. Most of what is in this video should apply to Linux as well, but any keyboard shortcuts might be a little bit different.

Thanks man! I appreciate the kind words. 🙏

Nope! You can use GitHub Pages with a standard GitHub account. That's what I'm using in this video. 😁

That's a really good idea! I think a gist or something similar might actually work better than a PDF, that way it's easy to copy and can be updated if needed. 👍

Thanks! I appreciate it. 🙏

Thanks for the sub! 🙏 I'll be making a video soon about essential Git commands when working with GitHub, which will include things like "git clone", "git pull" and "git push".

Every essential basic thing such as fork, clone, push, and public repository for beginners and intermediate levels.

I've got a Git tutorial on my channel that goes over the basics, but it doesn't get into the GitHub specific commands. I plan on making a video about the GitHub Flow soon, which will cover things like cloning, branching, pushing, merging and pull requests. Here's the Git tutorial if you are interested: ruclips.net/video/O4zb_bLRdPE/видео.html

I need to make sure you are paying attention! 😂

@@thecommoncoder great mentor, thanks so much:)

@uniquetaiwan No, thank you! 😊

when I inspect the page I only get <html> <head></head> <body></body> <html>

@@thecommoncoder Hey I posted it. Thanks in advance for any feedback and even posting this in the first place!

@@thecommoncoder The problem was that it wasnt saved! Thanks you have now allowed my to continue my HTML journey haha

@@theforoumfurry Awesome! Glad it's working now. 👏