Keyframes contributors???

[D4niel-dev]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Workflow Deployment

Discussion Details

Possible GitHub Releases contributor attribution bug

I think I might have encountered a bug with GitHub Releases....

Repository:
https://github.com/D4niel-dev/Orbit-beta

Release: v0.3.2-beta

The release page shows the GitHub organization Keyframes under the "Contributors" section. (Which i didn't add/edited in btw)

However:

• The repository has never received any pull requests from that organization.
• There are no commits authored by Keyframes.
• git shortlog only shows commits from my account (D4niel) and my local AI assistant account (dizel.ai).
• git remote -v confirms the repository only points to my GitHub repository.
• npm ls shows no dependency named "keyframes".
• git grep -i keyframes only finds CSS @keyframes declarations and changelog text referring to CSS animations.

This appears to be an incorrect contributor attribution rather than an actual contributor.

Steps that seem related:

1. Create a release from a Git tag.
2. Include changelog text mentioning CSS @keyframes.
3. GitHub Releases displays the GitHub organization "Keyframes" as a contributor.

Expected behaviour:

• Only actual contributors (commit authors, merged PR authors, or recognised contributors) should appear in the Contributors section.

Actual behaviour:

• The unrelated GitHub organization "Keyframes" appears as a contributor despite having no involvement with the repository.

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

[jrb00013]

yo so deep down what you're asking isn't "who contributed" — you're asking why the Contributors block on a Release is showing an org that never touched the repo.

i pulled your release notes on Orbit-beta v0.3.2-beta. you've got this line in there:

missing @keyframes scaleIn animation

github's markdown post-processor treats @something like an @mention. there's a real org called Keyframes, so it links them and dumps them into the release Contributors section. it's not a real contribution — it's just how github parses @. \@ does not save you (github eats the backslash before mention detection).

how to structure the notes so it does NOT credit them

any of these work:

1. inline code (easiest)
   write it as `@keyframes` so it's code, not a mention

2. zero-width space after the @ (what dependabot/renovate do)
   @​keyframes — looks normal, breaks the mention parser

3. don't use the @ at all
   say CSS keyframes / keyframes scaleIn animation — cleanest for changelogs

4. HTML comment break (ugly but works)
   @<!---->keyframes

edit the release body (or fix your changelog generator) and the fake contributor should disappear on the next render / edit save.

so yeah — you're not crazy, github really will "credit" whoever matches an @name in the release text. structure the notes so that string isn't a bare mention and you're good.