3 ms·
I was about to say "if private repo contributions count toward the code streaks, then someone could write a commit-bot to artificially inflate their code streak
by minimaxir 11y ago
I was about to say "if private repo contributions count toward the code streaks, then someone could write a commit-bot to artificially inflate their code streak completely undetected."
But the code streak is being removed too, which conveniently makes this potential loophole a nonissue! (However, it wouldn't surprise me if commit bots are used regardless to give an impression of coding-every-day on the graph.)
- nandhp 11y agoThere are also commit bots for other contribution graph hacks: https://github.com/gelstudios/gitfiti https://github.com/gelstudios/gitfiti
- sytse 11y agoIs there a risk that people still want a very green profile? With private repos you can use a commit bot without getting caught. I think public information should be based on public commits.
- newjersey 11y agoI have a public repo that has bogus commits to make my profile green. The repo is even very helpfully named if you take the two seconds dsto look at just the name. But as others have pointed out, Dropbox wants people to have private repos. Bizdev wins I guess.
- aavotins 11y agoWhy is it a risk? If you're applying for a job and potential employers see your all-green contribution graph, there is a very high chance they'll ask you to elaborate on that. At least now it is possible to actually show metrics for writing code that cannot be published or open sourced. Unfortunately quite a few recruiters care about it(because being a rockstar on github is a trend), but the initial screening process would filter out those with faked commit graphs.