Should you put tutorial projects on GitHub?

I would say to absolutely put your projects on GitHub. Having something to show them on GitHub is of benefit. Second, even if the project is based on a tutorial of which you have extended the functionality, it shows some of your own work extending current code.

What should go on your GitHub?

Write code that is readable, well-formatted, well-tested, well-documented and that displays a pragmatic approach via the commit history. Contribute to open source projects to show that you want to give back and can play well with others. Be sure to complete some projects.

What is GitHub and why should I use it?

Nearly every open-source project uses GitHub to manage their projects. Using GitHub is free if your project is open source, and it includes a wiki and issue tracker that makes it easy to include more in-depth documentation and get feedback about your project.

How do I contribute to a project on GitHub?

If you want to contribute, you just fork (get a copy of) a project, make your changes, and then send the project a pull request using GitHub’s web interface. This pull request is your way of telling the project you’re ready for them to review your changes. By using GitHub, you make it easier to get excellent documentation.

Do I need GitHub to work with a team?

If you only want to keep track of your code locally, you don’t need to use GitHub. But if you want to work with a team, you can use GitHub to collaboratively modify the project’s code. To create a new repo on GitHub, log in and go to the GitHub home page.

How do I make changes to the code base on GitHub?

Follow the steps below to get comfortable making changes to the code base, opening up a pull request (PR), and merging code into the primary branch. Any important git and GitHub terms are in bold with links to the official git reference materials. The first two things you’ll want to do are install git and create a free GitHub account.