An open-source repository hosting service, GitHub works like a cloud for code. It hosts your source code projects in a variety of different programming languages and keeps track of the various changes made to every iteration. The service does this using Git, a revision control system that runs in the command line interface.

             GitHub makes it easier to collaborate with colleagues and peers, and to look at previous versions of your work. Also, the wider community of programmers and hobbyists can download and evaluate your work.

            GitHub can integrate with common platforms such as Amazon and Google Cloud, as well as services such as Code Climate to track your feedback. It can also highlight syntax in more than 200 different programming languages.

            GitHub provides a community where programmers are constantly working to solve current problems and making solutions available to the public.

            When looking for a job, GitHub provides the best way to get recruiters to view your project, skills and the way you solve problems.

            The resume is dead. The internet has changed everything. GitHub now serves as your resume.

Ultimately, you want to show potential employers WHAT you can do instead of just telling them THAT you can do it. And employers LOVE being able to see it. This provides the best way for them to discover excellent problem solvers and good engineers.

            In the end, employers view the latter more favorably because the community views them more favorably.

How to include a GitHub project on a resume?

• • •  Select one project to show. Potential employers need to see just a single project. They’ll rarely go past it anyway. Make it a good one.
    •  Brush up your directory structure. Always follow the Simple Folder Structure Conventions for GitHub projects. This ensures that hiring managers spend more than five seconds looking at your code. Without diving too deep, your directory structure already shows your sense of architecture and design.
    •  Include a README. Make it clearly describe what the application does and tell the reader how to run it, build it and test it. Include screenshots (or even animated gifs) to demonstrate its functionality. Never assume people reading your code can find their way around. Reading a quick intro goes a thousand times faster than having to figure it out for yourself.
    •   Add a link to a website or an installer. If you have a web application project, run it online so everyone can see. For a desktop application, include a link to an installer to make it look more professional—even if the user will never run it. If you can’t be bothered to get a hosting and a website for your project, GitHub still has your back. It helps you create simple static websites and handles release management. Host your installers directly there.
    •   Make your code clean and easy to read. Comment appropriately. Most people won’t go as far as to read it, but you never know.

Remember, recruiters have very limited time (less than a minute), so get organized! Otherwise good candidates who fail to present themselves get overlooked.

Check out this example that recruiters can see about your project and your skills:

You can see this person works as a PHP developer. They have also done so many other things but most of the time they work with PHP:

Edureka

What is Git | What is GitHub | Git Tutorial | GitHub Tutorial | Devops Tutorial

SDET

How to work with Git & Github using Eclipse

Edureka

Git Commands With Examples | Git Tutorial | Git Branching & Merging | DevOps Training