Missing profile contributions from public repository commits on main (Repositories)

[ErasmusAndre]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Profile

Body

My profile contribution graph is missing a large number of commits from my public repository, even though I added and verified the relevant commit email addresses more than 24 hours ago.

A clear example date is:
14 March 2026: 33 commits by me that still do not appear correctly on my contribution graph

GitHub username: NoBadDays ( https://github.com/NoBadDays )
Repository: https://github.com/NoBadDays/erasmus.works
It's a Public repository, and commits are on Default branch: main

What I already checked:

The commits are on the default branch
The repository is public
The relevant commit emails are added to my GitHub account and verified
I waited more than 24 hours after adding the missing email addresses

One of the emails I used to commit was missing from my account, but I've added and verified it ~48h ago
Those commits don't seem to be showing on my profile.

I have ~300 commits on https://github.com/NoBadDays/erasmus.works in the last ~month, but on my profile it shows I only have ~100 commits

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[davex-ai]

hey @NoBadDays

Since you've already verified the emails and waited 48 hours, the most likely remaining cause is a Git identity mismatch between your local environment and your GitHub account settings.
Even if the email looks the same, a tiny difference (like a typo or an old configuration) in the commit metadata will prevent GitHub from linking it to your profile.

1. The "Author Email" Check

Run this command inside your erasmus.works local directory to see exactly which emails are attached to your March 14th commits:

git log --format='%ae' --since="2026-03-13" --until="2026-03-15" | sort -u

Compare the output strictly against the emails listed in your GitHub Email Settings. If an email appears in the logs that is not on your GitHub list (even by one character), those commits will never show on your graph.

2. The "Private Email" Conflict

Check if you have "Keep my email addresses private" enabled in your GitHub settings.

• If enabled, GitHub only attributes commits that use your ID+username@users.noreply.github.com address.
• If you committed using a standard email (e.g., name@gmail.com) while this setting was on, they may be blocked from the graph for privacy reasons.

3. Force a Graph Rebuild

Sometimes the contribution cache gets stuck. You can force a "pulse" to the graph by:

1. Creating a new, empty commit on the main branch:
   git commit --allow-empty -m "Trigger graph update" && git push
2. Wait about 5–10 minutes. This often triggers GitHub to re-index your entire commit history for that repository.

If there is a mismatch:

If you find that the March 14th commits used an incorrect email, you can fix your local setup for future commits:

git config --global user.email "your-verified-email@example.com"

Note: Retroactively fixing the graph for past commits requires a git filter-repo or a forced push, which is risky if you have collaborators.
Which email address did the git log command return compared to your verified list?

pls upvote

[ErasmusAndre]

1. Is correct and verified

2. "Keep my email addresses private" Used to be on, but I turned it off more than ~96h ago.

3. I've been making ~5+ commits a day over the past week, including this morning, but it's still not updated.

Not sure what to do, none of these have resolved my issue yet.
I'm the only person working on my repo, so if I need to rewrite some commits etc. or do risky things, I'm happy to do that.

[mecodeatlas]

Hey there! 👋

If your contribution graph isn’t showing what you expect, like missing commits, gray squares, or changes after merging, we’ve got a full guide that breaks down how it works and what counts as a contribution:

👉 Understanding Your Contribution Graph 🟩

It explains which activities turn squares green, how private contributions work, and the most common reasons contributions might not appear, like branch or email mismatches.

You can use it as a reference to check what might be happening with your graph!

If everything looks correct after reviewing the guide and the issue persists, we recommend opening a ticket with GitHub Support so the team can take a closer look at your account.

Hope it helps!

[rushikesh-bobade]

---

Hello @NoBadDays!

Since you are the sole contributor and are comfortable rewriting history, we can fix this. The reason your graph isn't updating is that turning off "Keep my email addresses private" does not retroactively change the metadata of the commits you already pushed. Those 300+ commits are still "signed" with the old privacy-protected email or a mismatched ID.

To fix the graph once and for all, you need to use a script to rewrite the author information for your entire repository.

Step 1: Run the Script

Open your terminal in your local erasmus.works folder and run this command (replace the placeholders with your exact GitHub verified email and name):

git filter-branch --env-filter '
OLD_EMAIL="your-old-hidden-email@users.noreply.github.com"
CORRECT_NAME="Your Correct Name"
CORRECT_EMAIL="your-verified-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

(Note: If you aren't sure what the "OLD_EMAIL" was, run git log -1 --format="%ae" on one of the missing commits first to find it.)

Step 2: Force Push to GitHub

Once the script finishes, your local history is fixed. Now you must push it to GitHub:

git push --force --all

---

Why this works:

GitHub's contribution graph is built by scanning the Author Email header of every commit. By rewriting the history, you are essentially "signing" those old commits with your newly verified email. Once you force push, GitHub will see these as "newly discovered" valid contributions and your green squares should appear almost instantly.

Let me know if you hit any snags with the script!

---

[itxashancode]

Why your commits aren’t appearing on the contribution graph

GitHub counts a commit toward your profile only when:

1. The commit is on the default branch of a public repository (or a private repo you have access to).
2. The commit’s author email exactly matches one of the verified email addresses on your GitHub account.
3. The commit is not excluded by any of the special‑case rules (e.g., commits generated by a bot, commits made via the web UI from a different account, or commits that are part of a pull‑request that was never merged).

If any of those conditions fail, the commit is ignored for the graph, even though it remains visible in the repository history.

Below is a step‑by‑step checklist you can run to locate the mismatch and fix it, followed with the exact commands you’ll need.

---

1️⃣ Verify the email used in the problematic commits

# Clone the repo (if you haven’t already)
git clone https://github.com/NoBadDays/erasmus.works.git
cd erasmus.works

# Show the author email for every commit on `main`
git log --pretty=format:"%h %ae %s" main

Look for the commits around 14 Mar 2026 (or any date you know is missing).

• If the email shown does not exactly match a verified address on your account → that’s why the commit is ignored.
• If the email matches but the graph still shows nothing, move to step 2.

Docs: https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/why-are-my-contributions-not-showing-up-on-my-profile

---

2️⃣ Confirm the email is verified on GitHub

1. Go to Settings → Emails.
2. Ensure the address appears under “Verified email addresses” (not just “Primary” or “Unverified”).
3. If you added it recently, GitHub may need up to 24 hours to propagate the verification to the contributions system. Since you said >48 h, the verification itself is likely fine.

---

3️⃣ Check for common exclusion reasons

Reason	How to test	Fix
Commit authored by a bot / CI system	Look at the commit’s author name/email – often something like github-actions[bot]@users.noreply.github.com.	Change the CI config to use your personal email (or add that noreply address to your verified list).
Commit made from a fork that you don’t have write access to	If you pushed from a fork you don’t own, contributions only count when the fork is your own or you have the

[rushikesh-bobade]

@NoBadDays Just a heads-up: the standard checklists mentioned above won't retroactively fix those 300 commits because the 'Private Email' block was active when they were first pushed. Since you're the sole contributor, that git filter-branch script I shared is the only way to re-sign those specific historical commits with your now-verified email. Once you force-push, those green squares should pop up almost immediately!

[ErasmusAndre]

This might not help others, but I changed my GitHub Username from NoBadDays to something else, and then when I checked my profile it was fixed.
I'm not sure if that was what fixed it, but my contributions show now