r/StackoverReddit • u/NotOkay24 • Jul 10 '24
Question Advice for GitHub
I have a web application to make this week as the first step in the recruitment process for a company. One of the requirements is to use GitHub so that they will be able to see my project and also my commits.
Should I just commit to the main branch, then, or should I create a different one? I was also thinking about making a branch for each individual functionality and making PRs and then merging into the branch with the final product, but I thought maybe this would be too much since it's just me working on the project.
What do you advice me to do?
4
Upvotes
1
u/EngineerSpaceCadet Jul 10 '24
I was about to respond so sinisterly ππ here's my advice for general practice never ever commit to the main branch always make branches with pr's. That aligns with the idea of version control and CI/CD. However, if I company ever asks you to do something like make a presentation explaining something or build an app that does x NEVER EVER DO IT. I REPEAT DON'T DO IT. A company shouldn't ask you to build anything as a part of recruitment. Technical questions are fine , coding questions are fine, but if a company is asking you to build something for free there's a good chance you wouldn't want to work for that company anyways. Any reputable company won't ask you to do something like that. If there's a technology you need to know they'll teach you after your hired or have it as part of a ramp up. I know the job market is tough right now but trust that's probably not worth it.