I would be alarmed if someone on my team or a potential new hire had a completely unbroken GitHub streak, let alone if they felt the need to maintain it via automation.
I would be alarmed if someone on my team or a potential new hire had a completely unbroken GitHub streak, let alone if they felt the need to maintain it via automation.
I think you made something “innocent” in intent without understanding the effect or impact it may have.
I presume you think having a longer commit streak is something that’s valuable, noteworthy, or shows some meaningful characteristic.
While potentially a seemingly harmless ideal, it says a bit about your lack of experience in the workplace and sets up a slippery slope to a toxic paradigm where programmers are expected to maintain commit streaks as part of their evaluation.
This is not a place you want to work and it’s not an expectation you want to hold yourself or others to.
At the end of the day if you want a completely green graph, you clearly have a mechanism to do so.
The point I’m trying to make is, having said graph will likely cause you more harm than you think, especially if you think “green squares” = “more likely to be hired for a desirable job.” It simply opens the avenue to questions regarding your intentions.
What I’d ask you to reflect on is, why does having a solid green graph feel more satisfying? What makes it so?
You’re also gamifying a system that could be interpreted as an attempt to misrepresent your genuine activity, while also completely missing the point of the activity graph.
In my experience, this would cause a seasoned interviewer to ask more prying questions about your work quality and its volume versus someone who had a less consistent pattern of GH activity.
Volume != Quality