Open rossabaker opened 4 years ago
Looks like a glitch from Github to me.
Looking at the actual commits per day looks fine (lists 180 for each pixel in that repo). Thus the patch in #8 itself seems to work as expected.
Maybe contact support and ask them what could be causing this. And maybe while at it also to abolish ICE. ;-)
mine isn't faded but after force reverting a branch then pushing again with much higher commit counts, only the two most recent days show counts greater than the previous value and the second most recent day is only registering about a quarter of the commits.
I've updated to the latest and now I have the same issue
I noticed the git log is showing my current timezone
Date: Sat Jun 6 12:00:40 2020 -0700
40 on 2020-06-06
but the github doc mentions Contributions are timestamped according to Coordinated Universal Time (UTC) rather than your local time zone.
not really sure how that could be a factor, but it seems like the most recent 10 weeks are being double counted.
switched default branch away and back and now it looks right :frowning_face:
Mine starts well and then degrades, but usually within an hour. Yours still looks good after four. :crossed_fingers:
Mine looks good after I run it, but several minutes later, some of the dates in E show 280 or 360 contributions instead of the expected 180. This makes the earlier letters blend in with the lighter green from other commits.
Maybe I ran it too many times testing PRs and got a stale cache. I didn't notice it before I tried #8.
Anybody else seeing this problem?