You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
So in my case, I open my github overview before I push any commit to my all github repo at 2 May and the stat like showing count back from zero. And after I push some commit at 2 may until this day, this is count back from 0 and not continue the counting from before..
To Reproduce
Steps to reproduce the behavior:
Open Your Github Overview
Don't Push Any Commit Before Step One
See Error
Try To Push Any Commit To Repo
Expected behavior
How to get this counting is continue and not start from zero. Actually this stat before (in 2023) was continue counting when it already push some commit after showing zero stat for current streak in daily mode
Screenshots
Desktop (please complete the following information):
OS: Windows 11
Browser Microsoft Edge
Version 22H2
Smartphone (please complete the following information):
Device: Xiaomi Redmi Note 9 Pro
OS: Android MIUI
Browser Xiaomi Browser
Version 11
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
So in my case, I open my github overview before I push any commit to my all github repo at 2 May and the stat like showing count back from zero. And after I push some commit at 2 may until this day, this is count back from 0 and not continue the counting from before..
To Reproduce
Steps to reproduce the behavior:
Expected behavior
How to get this counting is continue and not start from zero. Actually this stat before (in 2023) was continue counting when it already push some commit after showing zero stat for current streak in daily mode
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: