GitHub Community
my daily streak dot is not increasing #199273
Replies: 11 comments 7 replies
-
|
There are several common reasons why your GitHub contribution graph doesn't show green squares even though you're committing and pushing but most of the time GitHub takes a little time to update the contribution graph you should also check if
Could you share:
That will help identify the exact cause. |
Beta Was this translation helpful? Give feedback.
-
|
Alright so , repo is public ,it is my own repo and I have already checked every thing my Email is linked to github , My email is configured and is correct . |
Beta Was this translation helpful? Give feedback.
-
|
one more thing whenever i am creating a new repo, my green squares increases immediately .But my own commits in my own repo is not showing anything.I dont know what to do |
Beta Was this translation helpful? Give feedback.
-
|
Hi, If creating a new repository immediately increases your contribution graph, but commits to your existing repository do not, that usually means GitHub is recognizing your account activity but not counting those commits as contributions. Please check the following: Verify the commit email git log --format='%an <%ae>' -n 5 and confirm the email shown matches one of the verified email addresses on your GitHub account. Check the repository's default branch To help narrow this down, could you share: The repository URL (if public). The output of: git config user.name That information should help determine why the commits are not being counted on your contribution graph. |
Beta Was this translation helpful? Give feedback.
-
|
If creating a new repository increases your contribution graph immediately, the most likely cause is that the commits in this repository are not ending up on the repository's default branch as GitHub only counts commits that are reachable from the default branch (main/master) or gh-pages. So if you're committing to another branch and those commits haven't been merged into the default branch yet, they won't appear in your contribution graph. Also check whether the repository's default branch was changed at some point. I've seen cases where developers continue pushing to an old branch while GitHub counts contributions from the new default branch. If that's not the case, give GitHub some time as contribution graphs can occasionally lag behind, but based on the fact that new repositories are counted correctly, this looks more like a branch-history issue than an account or email issue. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, There are a few common reasons why your contribution graph (green dots) may not be updating even if you're committing and pushing regularly:
Could you confirm:
With that information, it will be easier to identify the cause. |
Beta Was this translation helpful? Give feedback.
-
|
Here is my project URL :-https://github.com/Ritwikcp-ctrl/School-management-.git |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
You can check the emails |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
see the command |
Beta Was this translation helpful? Give feedback.
-
|
This is one of the most common GitHub questions, and it almost always comes down to one of four specific causes. Walk through these in order — the first two account for the vast majority of cases. Cause 1 — Your commit email doesn't match a verified email on your GitHub account (most common cause)GitHub only counts a commit toward your contribution graph if the email address in the commit matches an email that is verified and linked to your GitHub account. Check what email your commits are actually using: git log --format='%ae' -5This shows the email address used in your last 5 commits. Check what emails are linked to your GitHub account: Go to GitHub → Settings → Emails (https://github.com/settings/emails) and check:
If they don't match, fix your local Git config: git config --global user.email "your-verified-github-email@example.com"
Cause 2 — The commits aren't on the repository's default branchGitHub only counts commits made to a repo's default branch (usually git branch -aIf you've been committing to a branch like Check your repo's actual default branch on GitHub: go to the repo → Settings → Branches — confirm the "Default branch" matches what you're pushing to. Cause 3 — The repository is private and you have the setting to hide private contributionsIf your repo is private, contributions only show on your graph if you've opted in to display them. Go to GitHub → Your Profile → Contribution settings (the gear/edit icon near the contribution graph) and check the box:
If this is unchecked, all commits to private repos are completely invisible on your graph, even though they're 100% counted internally and visible to you in the repo itself. Cause 4 — The repository is a fork, and you haven't opened/merged a Pull RequestIf the project is a fork of someone else's repository, plain commits pushed to your fork do not count toward your contribution graph by default. GitHub only counts fork contributions when:
If you're just committing locally to your own fork and pushing, without ever opening a PR against the upstream repo, none of that shows up as a contribution. Less common causes to check if the above don't apply5. The commit date is in the future or far in the past — GitHub's graph uses the author date in the commit, not the date you pushed. If your system clock was wrong when you committed, or you used git log --format='%ad' -56. You're not actually a collaborator/contributor by GitHub's criteria — for organization repos, contributions sometimes take a short delay to be indexed and reflected on the graph (usually resolves within 24 hours). How to verify which cause applies to you — fastest diagnosticRun this and compare against your GitHub email and target branch: git log --format='%h %ae %ad %D' -10 --date=shortThis shows, for your last 10 commits: hash, author email, author date, and branch refs — letting you check all of the above at once. Fixing past commits that used the wrong email (if Cause 1 applies retroactively)If you've already pushed commits with an unverified/wrong email and want them to count, you need to rewrite the commit history with the correct email, then force-push: git filter-branch --env-filter '
OLD_EMAIL="wrong-email@example.com"
CORRECT_NAME="Your Name"
CORRECT_EMAIL="your-verified-github-email@example.com"
if [ "$GIT_COMMITTER_EMAIL" = "$OLD_EMAIL" ]
then
export GIT_COMMITTER_NAME="$CORRECT_NAME"
export GIT_COMMITTER_EMAIL="$CORRECT_EMAIL"
fi
if [ "$GIT_AUTHOR_EMAIL" = "$OLD_EMAIL" ]
then
export GIT_AUTHOR_NAME="$CORRECT_NAME"
export GIT_AUTHOR_EMAIL="$CORRECT_EMAIL"
fi
' --tag-name-filter cat -- --branches --tags
git push --force --all
Summary checklist
Start with Cause 1 (email mismatch) — it's responsible for the large majority of "my commits aren't showing up" reports. Hope this helps — if it answers your question, would you mind clicking "Mark as answer" so others searching for the same thing can find it quickly? |
Beta Was this translation helpful? Give feedback.
-
|
Thank You for the reply , sir I have checked everything and evrything is correct , Every thing is up to date. |
Beta Was this translation helpful? Give feedback.
-
|
Still not showing my streak. |
Beta Was this translation helpful? Give feedback.
-
|
Since the standard checklist didn't resolve it, the cause is likely one of the less obvious ones. Let's narrow this down properly rather than re-listing the same checks — a few clarifying things first, then the deeper causes to check. Quick clarification that changes the diagnosis"Streak" specifically refers to consecutive days of contributions, which is a different (and stricter) thing than the contribution graph simply showing a green square for today. Two distinct possibilities:
Worth confirming which one you're seeing before going further: is today's square greyed out/empty, or is it green but the streak number text isn't going up? Deeper causes beyond the original checklist1. Timezone mismatch between your commit and GitHub's day boundary (very common streak-specific cause)GitHub's contribution graph and streak calculation use UTC to determine which calendar day a contribution belongs to — not your local timezone, and not the commit's local timestamp as you perceive it. If you commit late at night in your local timezone, it may register as the next day (or the previous day) in UTC, which can make it look like you "missed" a day even though you committed every single day locally — breaking the streak from GitHub's perspective even though your commits look continuous to you. Check this: git log --format='%ad' --date=iso-strict -5Look at the actual UTC offset in the timestamp and compare against midnight UTC boundaries. If your commits cluster right around 00:00 UTC, this is very likely your issue. There's no config fix for this — it's how GitHub's graph works — but it explains an otherwise-confusing "I commit every day but my streak keeps resetting" symptom. 2. You're checking the streak number itself, but it has known display lagGitHub's streak count (separate from the graph squares themselves) has a documented history of lagging behind actual contribution data due to caching on GitHub's end — the underlying graph data can be accurate while the displayed streak number is stale. This typically resolves within 24 hours without you doing anything. If your most recent qualifying commit was very recent (today or yesterday), this delay alone could explain it. 3. Re-confirm it's not Cause 4 from before — fork without a merged PRIf "my own project" is actually a fork of another repository (rather than a repo you created from scratch), this is worth double-checking explicitly, since it's easy to misremember whether a repo started as a fork: git remote -vIf you see the remote pointing to a repo you don't own, or if visiting the repo on GitHub shows "forked from X" under the repo name, you're in fork territory — and per Cause 4, plain commits to your fork don't count toward contributions or streaks unless they're part of a merged (or in some cases opened) pull request back to the upstream repo. 4. Double check you re-ran the diagnostic command and actually compared the outputThis sounds basic, but it's worth being explicit: did you run git log --format='%h %ae %ad %D' -10 --date=shortand literally compare the email address shown against https://github.com/settings/emails, and the branch shown ( If you can share the output of that command (with anything sensitive redacted), it would pinpoint this immediately rather than continuing to guess between the remaining possibilities. Most likely next stepGiven you've already been through the original four causes, the timezone/UTC day-boundary issue (Cause 1 above) is the single most common reason someone says "the graph/contributions show up but my streak isn't increasing" specifically — as opposed to "no contributions show at all," which points back to the original email/branch/fork causes. If you can confirm exactly what you're seeing — empty grey square for today vs. a green square but stagnant streak number — that will determine which path to debug further. Hope this narrows it down — if it answers your question, would you mind clicking "Mark as answer" so others searching for the same thing can find it quickly? |
Beta Was this translation helpful? Give feedback.
-
|
Alright , so whenever i am forking or making some new repo the green square box is showing immediately but when i am making commits in my own repo, does not show any green squares . |
Beta Was this translation helpful? Give feedback.
-
|
┌──(ritwikrai㉿kali)-[~/Desktop/Startthefuckingup/school-management/school] |
Beta Was this translation helpful? Give feedback.
-
|
see, i run the command. Well i checked this before. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Issues
Body
Hey , i am continiously doing my contribution on my own project, committing pushing but my green dot is not increasing why ?
Beta Was this translation helpful? Give feedback.
All reactions