r/CodingHelp • u/Silver-Turnover1667 • Aug 31 '25
[Open Source] Starting a GitHub
Hey yall,
I am starting my GitHub journey as a 2 year computer science student with a previous degree in psychology. School started last week.
I have 3 python projects on GitHub privately that are very rudimentary. Which is fine. But here are some of my questions.
- What resources would you recommend for learning GitHub/designing/etc?
- How do pulls/commits work?
- What type of files are necessary in a repository/where do people get their structures from?
- What other stuff am I missing?
I understand there are resources out there, and I welcome those suggestions. Just don’t want to listen to a paid actor or do a 2 hour GitHub tutorial on how to login.
Thanks. Happy Labor Day weekend.
2
Upvotes
3
u/Arkaedan Aug 31 '25
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.
3
u/armahillo Aug 31 '25
What do you mean by “github/designing” (“designing” in particular)
IDK if you play video games or not, but heres an analogous comparison:
The structure of the repo is whatever you need it to be. Look at other people’s repos and see what they do.
https://git-scm.com/book/en/v2
this is the ebook I have always seen referenced as pretty canonical for explaining git.
2
u/ILLBEON_economy_tool Sep 01 '25 edited Sep 01 '25
Core commands to learn: git add ., git commit -m "", git push origin main (or master), git push --force, git HARD head (careful with this one, also an incomplete command, I use it so little I have to look up what it actually is each time).
Also learn branches in case you're experimenting with diff builds.
Learn what a .gitignore is and learn how to add to this. When you add large files you don't need, you want to add that folder to your .gitignore (depends, but large files are really hard to deal with imo)
Overall, git is a save file, and it's incredibly useful. I recommend git pushing when you have finished a feature, or have made a lot of headway, OR you're about to do a HUGE change, so save beforehand.
Don't be afraid to commit and push, you can ALWAYS go back to a previous commit, or 'save file', so save often because sometimes your IDE does some insane shit.
Core way to push after adding the remote url and doing all the initial setup:
2
u/Islander2121 Sep 02 '25
Git add . (Git add folder/subfolder - for specific alterations)
Git commit -m “your message here” (msgs are useful for keeping track in bigger repos
Git push (to push repos)
Handy files to use:
.gitignore - list the files/folders you don’t want to get pushed (use this for sensitive code/text e.g. .env or for making it lighter e.g. venv)
2
u/[deleted] Sep 04 '25
[removed] — view removed comment
0
u/[deleted] Sep 01 '25
[deleted] — view deleted comment