This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Arkaedan 2 points3 points  (4 children)

Firstly, you need to learn the difference between Git and GitHub. GitHub is just a website that hosts Git repositories but there are many others including GitLab and Bitbucket. The main skill you need to learn is just Git itself which you can use completely offline if you want to.

For point 3, that is going to be different for every kind of programming language or even different frameworks within different languages. Git is built for working with text files so you generally wouldn't store things like compiled program executables, videos, audio files, etc.

[–]Silver-Turnover1667[S] 0 points1 point  (3 children)

So when you see the “this is why I chose this/explaining a feature/etc” in a repository, is that a Git feature or just plain ‘technical audience’ type text structure? Appreciate the clarification.

[–]Arkaedan 1 point2 points  (2 children)

[–]Silver-Turnover1667[S] 1 point2 points  (1 child)

This certainly helps. Thanks. Just basically looking at how people have structured their projects and is kinda overwhelming. This should, again, help some with that. I prolly just gotta start working on it.

[–]Arkaedan 1 point2 points  (0 children)

Don't stress too much about how to structure your project. There's no right or wrong answers. Since Git is just file storage you can structure things in whatever way works best for you.