Security Advisory Credit not syncing to Profile

[omarkurt]

Select Topic Area

Bug

Body

Hi GitHub Support Team,

I would like to report a bug regarding the synchronization of Security Advisory credits to the user profile.

Issue Summary:
Credits accepted while an advisory is "Private" do not automatically appear on the user profile after the advisory becomes "Public". The profile update seems to get stuck until a completely new/unrelated credit event triggers a system-wide refresh.

My Experience (Steps to Reproduce):

1. I was credited on advisory GHSA-8v65-47jx-7mfr (CVE-2026-21859).
2. I accepted the credit while the advisory was still in "Private/Draft" mode (approx. 4 days ago).
3. The advisory was published and became "Public" today.
4. Despite the advisory being public, the credit did not appear on my profile for hours.
5. I attempted to force a refresh by editing my profile bio (standard cache invalidation trick), but it did not work.
6. The Fix: Moments later, I accepted a credit for a completely DIFFERENT, new vulnerability.
7. Immediately after accepting the NEW credit, the OLD (stuck) credit also appeared on my profile.

Observation:
It seems that the "Publish" event of an advisory does not properly trigger the "Recalculate Credits" job for users who had already accepted the invite during the private phase. It required a new "Accept" event on a different repo to unclog/refresh the cache.

Impact:
Researchers are confused why their credits are not showing up after publication, leading to unnecessary support tickets.

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