Really sorry — this is genuinely stressful, and you're doing the right things. A few honest, practical notes from what I and others have seen with account suspensions:

1. Nobody here can lift the suspension. Only GitHub Support / Trust & Safety can. So the goal of everything below is just to make sure your ticket reaches the right team and isn't waiting on something from you.

2. There is no published SLA for suspension appeals. From the public reports I've seen, the realistic range is anywhere from a few days to a few weeks. Two days with no human reply is unfortunately normal and does not mean your ticket was lost. The auto-reply you got after submitting is the receipt; if you have a ticket number, hang on to it.

3. Use the right form, once. The correct entry point is the appeals form, not generic support:

• Appeal an account or content restriction (sign in as a different account is fine — you reference the suspended username in the form)
• Or the general flow: support.github.com/contact → "Account, Login, & Profile" → "Restored / restricted account"

Do not open multiple tickets for the same issue — duplicates get merged and can actually push you to the back of the queue. If you already submitted one, just reply to that thread with any new info instead of filing a new one.

4. What to include in your appeal (this is the part that actually speeds things up):

• The exact username (felichio) and the email on the account (fsafaridis@hotmail.com).
• A short, factual timeline (what you wrote above is good — push on Tue evening worked, Thu morning pull failed).
• Mention the VS Code "GitHub Pull Requests" extension auth loop explicitly, and that you suspect it may have triggered an abuse/rate-limit heuristic. This is a real, known failure mode — the extension can spam token requests in the background, and that pattern can look like credential-stuffing to automated systems. Naming it gives a reviewer something concrete to check.
• State clearly that you'd like the account reinstated and, if there was a TOS issue, you'd like to know what it was so you can correct it.
• If your work is blocked, say so plainly ("this affects my employment at [org]") — they do triage on impact.

5. Things to not do while you wait:

• Don't create new accounts to work around the suspension. Operating evasion accounts is itself a TOS violation and will get the new account banned and can hurt your appeal. (Creating one throwaway just to post in Discussions, as you did, is fine — that's not evasion.)
• Don't post the ticket number publicly.
• Don't email random GitHub employees on LinkedIn/Twitter — it doesn't speed things up and can confuse the ticket routing.

6. Protect what you can right now:

• If you have local clones of your important repos, push them as bundles (git bundle create repo.bundle --all) to a USB drive or another git host as cold backup. Your local clones are not affected by the suspension.
• If colleagues or collaborators have forks of your repos, those forks still exist and contain your history. Worst case, your code is not gone.

7. About the extension theory: plausible but unprovable from outside. If it's true, reinstatement is usually straightforward once a human reviews it — automated abuse triggers are explicitly reversible. That's actually the good scenario.

Hang in there. Two days is well within the normal window. Reply on your existing support ticket once with the timeline + the VS Code extension detail and then wait — refreshing or filing new tickets won't make it faster, and unfortunately this community discussion can't escalate it.

Drafted a calm, practical reply: set realistic expectations (only Support can reinstate, no SLA, 2 days is normal), pointed to the correct appeals form, listed what to include in the appeal (with the VS Code extension auth-loop angle highlighted as a concrete lead), warned against counterproductive actions like creating evasion accounts or duplicate tickets, and suggested local-clone backups as risk mitigation.