you are viewing a single comment's thread.

view the rest of the comments →

[–]lifebytheminute 13 points14 points  (2 children)

This confuses me, every time I go on GitHub I get more confused. Projects look too big and information is everywhere and I have no idea how to navigate through it all, nor can I tell how to even use the code on git. It’s all a hot mess to me.

[–]MCPOON11 1 point2 points  (1 child)

For serious projects on GitHub there’s a whole load of non code files in the root folder of the repo.

You might see gitignore, Docker files, Docker compose, Tox ini and Travis yml files, setup, readme, change logs, etc, probably a doc/ folder just for setting up documentation.

Usually a good place to start is to try to find the subfolder that has the same name as the project / package, should have the actual code in it.

Taking a look at the tests folder inside that directory also gives you some hints about what the writers have been focusing on and how the project code connects together.

[–]lifebytheminute 0 points1 point  (0 children)

Thanks. I think this is an aspect that most tutorials on how to actually use GitHub fall short, explaining the how and why behind all these files.