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
@jstrieb I've been using GitHub Stats for about four months, and it has been working fine. However, after an update on August 14, 2024, the lines of code, which previously totaled 801,844, suddenly dropped to 0 see - 5f5a20a. I tried troubleshooting the issue myself and followed the discussion in issue #45, but I couldn’t quite understand what went wrong.
It works perfectly fine when I manually run the workflow see - 15daa40, but when the workflow runs automatically, the lines of code reset to zero again see - f921954.
The text was updated successfully, but these errors were encountered:
pushpakumar02
changed the title
Lines of Code Reset to 0 on August 14
**Title:** Lines of Code Reset to 0 When Automatically Committed, But Works Fine When Manually Run
Aug 27, 2024
pushpakumar02
changed the title
**Title:** Lines of Code Reset to 0 When Automatically Committed, But Works Fine When Manually Run
Lines of Code Reset to 0 When Automatically Committed, But Works Fine When Manually Run
Aug 27, 2024
+1 I'm having the same issue.
Because I changed my username around that time, I thought that might be the cause. But I added some logging, and it seems like the contributors are loaded correctly, but somehow the weekly stats are either missing or zero.
Description:
@jstrieb I've been using GitHub Stats for about four months, and it has been working fine. However, after an update on August 14, 2024, the lines of code, which previously totaled 801,844, suddenly dropped to 0 see - 5f5a20a. I tried troubleshooting the issue myself and followed the discussion in issue #45, but I couldn’t quite understand what went wrong.
It works perfectly fine when I manually run the workflow see - 15daa40, but when the workflow runs automatically, the lines of code reset to zero again see - f921954.
The text was updated successfully, but these errors were encountered: