Had a question for those experienced in the field/recruiters. I'm a current college student close to graduating and am working on creating a github that I can put on my resume. Wanted to ask the following questions: 1.) Should I include the commit history on the projects that are going to be visible on my github? A couple are group projects and some are my own, with most of the commits being non-professional/messy (still contain PR's, merges, branches etc. just shitty commit messages and stuff like that). Should I include these to show that at least know how to use git, or will the shitty commits make the recruiter/engineer think I don't know what I'm doing? I'm considering cloning all my projects and just having each repo as my final version with 1 commit, but don't know if it'll look faked/bland in terms of my skills or if it'll look more professional/clean. Edit: msg received, thx for the help!
No one has the time or desire to go through your commit history
Yes, and also listed out all the names of your ex will be helpful
their IG usernames would be better
If I ever see a resume with a commit history on my desk, it's going in the trash, not even reading it.
I once received a resume at a uni career fair with a list of papers READ, not published.
Bwahahaha, nice.
It doesn’t matter most ppl barely glance at your GitHub. Exception is maybe really small companies who might look into it in detail
I was wondering this as well. I thought it would be a good idea since so many people applying for SWE jobs are not actual software developers. 🤔 Edit: "not actual software developers" e.g. people like me 😅😉
No