Github Student Pack Broken Verification Bot: False Rejections Due to Turkish Characters and Unrecognized Date Formats #196156
Replies: 1 comment
-
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Verification Help & Guidance
Hi everyone,
Hi everyone,
I am writing this because I am incredibly frustrated with the automated verification system. Every single year, I experience the exact same issue when trying to renew my student benefits, and it is exhausting having to fight with a broken bot.
Here are the recurring problems:
1. The OCR Cannot Read Turkish Characters:



My GitHub Profile name, my GitHub Billing name, and the name on my official student documents are an EXACT, 1:1 match. Despite this, your automated system constantly rejects my application citing a "name mismatch". It is painfully obvious that your verification bot is malfunctioning and failing to process non-English/Turkish characters on official documents.
2. Ridiculous "Date Format" Errors:
In one of the rejections, the bot complained about the "date format" not being standard. For context, official documents in Turkey strictly use the Day-Month-Year (DD/MM/YYYY) format. Let me be clear: this is an official government/university document. It is not my responsibility to alter or "standardize" the official date format of my country just because your bot might only understand Americanized (MM/DD/YYYY) formats. It is GitHub's responsibility to ensure its global verification system can actually recognize and evaluate official international documents.
3. I Have Exhausted All "Troubleshooting" Steps:
To anticipate any generic support advice: I have repeatedly tried submitting various forms of proof, including my School ID, a Turkish transcript, a multilingual transcript, and even live captures of my university student panel. I have attempted this process endlessly using different browsers, different devices, and different cameras. I even meticulously updated my GitHub Profile and Billing Information to match the documents character-by-character, strictly following the exact uppercase/lowercase formatting on my ID.
Nothing works. We shouldn't have to waste days trying to figure out how to trick an AI into seeing what is clearly written on a paper. The automated bot is actively penalizing international students for having localized characters and official state date formats.
Please fix your OCR system, adapt it to international standards, or at least provide a direct manual review option when the bot inevitably fails. I need a human staff member to review my application and approve it, because the bot clearly cannot do its job.
Beta Was this translation helpful? Give feedback.
All reactions