GitHub Support is Avoiding My Billing Issue

[arditibless-ui]

Discussion Type

Bug

Discussion Content

I want to share my experience because it shows how GitHub Support handles consumer complaints in a way that feels designed to make people give up.

On May 21, 2026, I paid $123.45 under the old subscription model.

On June 21, 2026, I was billed again for $408.82, even though my subscription was paused and my usage dashboard shows “No usage found” in June.

This is a duplicate billing error caused by GitHub’s June 1 migration to token‑based billing, mislabeled as a subscription fee.

I opened a support ticket with all the evidence attached. GitHub ignored it for over a week. When I tried to open a second ticket (because the first was unanswered), they closed it immediately with an automated message saying it was a “duplicate.” In other words:

They didn’t fix the issue.

They didn’t even acknowledge the duplicate billing.

They just closed the second ticket to make their queue look cleaner.

This is not support — it’s a tactic to wear customers down until they give up. Instead of solving the problem, they consolidate tickets and avoid responsibility.

I’ve already escalated to CCPC Ireland (the regulator) and tried contacting Microsoft Ireland Operations Ltd., but GitHub’s behavior here shows a pattern: stalling, deflecting, and ignoring individual users.

Consumers deserve better than this.

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