Commits on default branch are not counted as profile contributions

[AmirAbitov]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Issues

Body

Repository: https://github.com/AmirAbitov/expense_tracker_oop
Commit hash: 7d303ddd456e5930d2f35d138e5d1975e07e3ad3
Email verified
Public repository
Default branch main
Author email matches GitHub account
git remote points to

repository

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[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. ⭐

[LuShadowX]

The author email on those commits isn't connected to your account, so GitHub can't attribute them to you. expense_tracker_oop 404s now, but the same pattern is in expense_tracker_CLI and your other repos:

gh api /repos/AmirAbitov/expense_tracker_CLI/commits \
  --jq '.[] | "\(.commit.author.email) -> \(.author.login // "UNRESOLVED")"'

aabitov96@email.com -> UNRESOLVED

Compare with developer-path-to-do-with-json, which has both kinds:

118526634+AmirAbitov@users.noreply.github.com -> AmirAbitov   x2
aabitov96@email.com                           -> UNRESOLVED   x2

The ones that resolve were made through the web UI, which uses your GitHub noreply address. The ones from your machine use aabitov96@email.com, and author comes back null in the API — GitHub has no account matching that address. That's what "author email matches GitHub account" is checking, and it's the one box that isn't actually ticked.

Worth a close look at that domain: @email.com, not @gmail.com. If that's a typo in your git config, every commit you've made locally carries it.

Two ways to fix it, from Why are my contributions not showing up on my profile? — "Commits must be made with an email address that is connected to your account on GitHub":

Recover the existing commits — add aabitov96@email.com under Settings → Emails and verify it. The docs say "Your contributions graph will be rebuilt automatically when you add the new address", allow up to 24 hours. This only works if you can actually receive mail at that address.

Or fix it going forward — point git at your noreply address:

git config --global user.email "118526634+AmirAbitov@users.noreply.github.com"
git config --global user.name "AmirAbitov"

New commits will count immediately. Old ones stay unattributed unless you rewrite their author metadata, which isn't worth it for a contribution graph.

Check what you're currently set to with git config --global user.email — that's almost certainly where the typo lives.