GitHub Education verification: templated rejections that don't match submitted evidence, and "remote learning" option that doesn't actually work

[wuyilingwei]

🏷️ Discussion Type

Question

💬 Feature/Topic Area

Benefit Activation/Waiting

Hi everyone,

I've applied for GitHub Student Developer Pack verification for @wuyilingwei five times since June 4, 2026. Posting the actual rejection text below, along with the source documents, because I think the pattern speaks for itself — I'd invite anyone reading this to look at the attached PDFs directly and judge for themselves whether the school name and date are present.
Issue 1: The documents clearly contain the school name and a generation date — the rejection reason is simply false.
Attached are the two most recent Confirmation of Enrolment letters I submitted. Both prominently display "University of Toronto" as a letterhead and header, both list the issuing campus (University of Toronto Mississauga), and both carry an explicit "Letter Generated: [date]" field plus a DLI registration number. The claim that these documents don't demonstrate current academic affiliation with a dated, named institution does not hold up against the actual attached files.
Issue 2: Requiring a photograph of an official digital document is a self-inflicted problem.
These letters are issued by the university as official electronic PDFs, downloaded directly from the institution's own portal — not paper documents. If GitHub's process requires applicants to photograph such documents rather than accepting the original digital file, that introduces exactly the kind of image blur, glare, and legibility issues the rejection reasons complain about ("document does not appear to contain X," "image does not appear to be legible") — problems the verification system creates for itself by refusing clean, original digital evidence in favor of a photo of a screen. That's not a shortcoming of the evidence; it's a shortcoming of the intake process.
Issue 3: The "remote learning" option appears to do nothing, even with supporting evidence.
On June 4, I was enrolled in a Summer 2026 remote/online session. I explicitly selected the "remote learning" option during submission, and additionally provided a screenshot from my university's official course registration system explicitly showing the course delivery mode as "Online." Despite this, I was rejected with:

"You appear not to be near any campus location for the school you have selected... You must configure your browser and operating system to allow location access. You may not use a VPN."

I selected the remote-learning option specifically to account for this, and supplied direct institutional evidence confirming the course was online. If that combination isn't sufficient, what evidence would be?
Issue 4: Identical name/date rejection reasons across five submissions, regardless of what changed.
Across all five rejections (June 4 ×2, June 23, July 1 ×2), the following two reasons appear almost verbatim every single time:

"document does not appear to include a date demonstrating current academic affiliation"
"first/last name doesn't match GitHub billing information"

For the two most recent submissions, I provided two official University of Toronto Confirmation of Enrolment letters — one covering Summer 2026 (May 1–Aug 31, 2026) and one covering Fall-Winter 2026-2027 (Sept 1, 2026–Apr 30, 2027) — together spanning continuous enrollment including the exact date of submission. The "no current date" rejection is factually incorrect for these submissions, as anyone looking at the attached files can verify.
On the name issue: my legal name is in pinyin format, rendered as "Siyu Lei" (given name / surname) on every official document, exactly matching university records. I have tried every reasonable permutation in GitHub billing — "Siyu Lei," "Lei Siyu," with and without spaces — and received the identical generic rejection every time, with zero indication of which specific field or character supposedly doesn't match.
The core problem: these rejection reasons do not change in response to what I actually submit — not the remote-learning selection, not the added course-registration screenshot, not two enrollment letters spanning the full year with clear dates and institution names, not any permutation of my legal name. That strongly suggests either (a) no human is reviewing the documents — each application is rejected against a static checklist within under a minute regardless of content, or (b) the automated matching/OCR logic is fundamentally unreliable and there's no fallback to human review when it fails repeatedly across multiple submissions.
GitHub markets the Student Developer Pack as the primary or sole verification pathway for numerous partner services (Copilot, JetBrains, DigitalOcean, etc.). If that's the role this program plays, the verification process should carry a corresponding level of accountability — not a rejection loop with contradictory, unchanging boilerplate, a requirement to degrade clean digital evidence into photographs, and no path to human escalation.
Direct questions for GitHub staff:

Is there any human review step, or is this fully automated?
Why does the process require a photograph rather than accepting an original digital document directly from the institution?
If a "remote learning" option exists, why does providing both that selection and direct institutional proof of online enrollment not exempt an applicant from location/VPN checks?
What specific field is flagged as a name mismatch — can this be shown to the applicant rather than a generic message?
Is there an actual escalation path beyond "resubmit and get the same rejection again"?

Confirmation of Enrolment (3).pdf
Confirmation of Enrolment (4).pdf

[Light0777]

this is a pretty common type of issue with student verification systems.
They usually rely heavily on OCR + automated checks, and international names, digital documents, remote students, and university formats are exactly where those systems tend to fail.

try posting about this on X