Feedback is not for the community

[TheBadkraft]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

I was given an option of community engagement or giving feedback. I selected feedback. So my expectation is that I get a feedback form indicating a closed channel of communication between me and someone at github.

looks like you have changed how tokens are charged, costs accrued, etc., sometime over the last 30 days. what I paid last month didn't go near as far this month. do you make changes to these prices and not let people know? I have entire workflows set up and now they don't complete the tasks like they used to.

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

[Shivang9983]

"You aren't imagining things—GitHub actually rolled out a massive change to its pricing model. On June 1, 2026, they completely killed off the old 'flat-rate request' billing system and shifted everyone to a usage-based model built around GitHub AI Credits.

[TheBadkraft]

I'm building an EdgeAI system. the singer everyone else figures this out, the better. and these premium pay services will be choking on dust. Bait 'n switch ...

…

On Tue, Jun 23, 2026, 14:00 shivang kumar ***@***.***> wrote: "You aren't imagining things—GitHub actually rolled out a massive change to its pricing model. On June 1, 2026, they completely killed off the old 'flat-rate request' billing system and shifted everyone to a usage-based model built around GitHub AI Credits. — Reply to this email directly, view it on GitHub <#199956?email_source=notifications&email_token=BFQIM5ODGAURKJUDXYDOSK35BLHVZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZUGEYTKNBSUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVRTG633UMVZF6Y3MNFRWW#discussioncomment-17411542>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFQIM5N3U6GGZ3GMFOKDVKD5BLHVZAVCNFSNUABIKJSXA33TNF2G64TZHMZTAMJVG4ZTGNBUHNCGS43DOVZXG2LPNY5TCMBTGA4DEMZZUF3AE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Farhan71140]

Thanks for sharing your experience. To clarify: the “Feedback” option is meant to send product feedback directly to GitHub, not to open a private support channel. Community engagement posts appear here in Discussions, while feedback is routed internally.

Regarding billing: GitHub Copilot recently moved to usage‑based pricing. This means credits are consumed differently depending on the model type (e.g., GPT vs Claude) and reasoning level. Even if your workflows haven’t changed, the token costs may vary month to month because:

• Different models have different token pricing structures.
• Reasoning levels affect how many tokens are processed internally.
• System overhead tokens are always included, even for short prompts.

GitHub does announce major pricing changes in Copilot News and Announcements, but usage fluctuations can still occur depending on the model you select. If you believe your credits are being consumed abnormally, the best step is to open a support ticket with GitHub and include details of your workflows and usage logs so they can investigate.

In short: feedback goes to GitHub internally, not as a private form, and the higher costs you’re seeing are tied to usage‑based billing changes. Escalating to GitHub Support is the right way to get clarity on your specific case.