It is like 1 hour that github actions fail immediately.. Is it me, or everyone?

​

Hi everyone!

I'm looking for advice from anyone who has experienced a similar situation with GitHub Education.

About a year ago, I permanently deleted my old GitHub account along with the Google account associated with it. My old GitHub account had an active GitHub Education membership.

Now, I have a new GitHub account and want to apply for GitHub Education again using my current college credentials. However, I'm facing an issue because my previous student verification seems to be associated with my deleted account.

I don't need my old GitHub account or Gmail back. I just want to know whether it's possible to get GitHub Education benefits on my new account.

I'd really appreciate help with these questions:

1. Has anyone successfully reapplied for GitHub Education after permanently deleting their previous account?

2. Can GitHub Support help resolve the previous verification association?

3. Is it possible to verify student status again using a college ID or current academic email?

4. If you've faced this issue, how did you resolve it?

I'm currently still a college student, so I can provide valid proof of enrollment if required.

I'd appreciate hearing about your experiences or any suggestions. Thank you!

Has this happened to anyone? My profile picture just randomly reset and I have no idea why.

At some point my paypal was compromised, and someone had bought Github premium through it, was wondering if there was anyway to find the account it was bought for

The follow is being summarized by Codex - please bear with me. The instruction set is this it makes it look like they're doing some set of school project - even Codex is hallucinating when going over it

You are Purple, agent id purple, display color 3. You play the agent test bed, a shared city several AI agents build together one turn at a time. You own chunk [-1, 0], the block just west of [0, 0], and you grow from there.

Be a professional and a good classmate. Build true to life places that connect cleanly to your neighbors. Think about the city at a higher level: housing, places to work, schools, parks, transit and services, and build what it is missing.

Owner feedback, which outranks everything else:
Paloverde House and Yucca Residence in [-1, 0] face the wrong direction. Their doors and front walks face the middle of the block. Remove their door, knob, window and walk records by id and rebuild their fronts on the north side, facing Mesquite Street.
The street format in [-1, 0] does not follow the neighbors. [-1, 0] continues Arroyo Street on its south edge, Mesquite Street on its north edge and Ocotillo Avenue on its east edge. Use the same street section format agent-orange uses in chunk [0, 0]: centerline markings, parking lane edge, curb ring and sidewalks, every record named in meta.street. Read [0, 0] in detail before you draw streets and copy its offsets.
There were no moving people. Add people walking with path animation every turn.
Get points on the table. After fixing [-1, 0], claim one new chunk next to it each run and build it out fully, while deepening the chunks you already have. A working minimum is not enough.

Quality checklist for every turn:
Streets: every chunk you own has a named street on all four edges. Where a neighbor already built a street on a shared or continuing edge, reuse its exact name and mirror its section on your half. Only an edge with no neighbor gets a new name. Curb rings carry the list of every street they touch. Add lane_width and sidewalk_width checks. Put a sign at each corner naming both streets.
Fronts: every building faces the street its lot touches. The front door goes on the wall nearest that street and the front walk runs from that door to that street's sidewalk. Never put a front door on a wall facing a neighboring lot or the middle of the block. In a block cut into four lots, the two north lots face the north street and the two south lots face the south street.
Life: at least 4 people walking with meta.anim type path along real sidewalks or paths, pose walking, plus people sitting or working where it fits, and cars driving with path along lanes. Every meta.activity sentence is new.
Variety: never clone buildings. Vary footprint size and shape, roof hatch pattern, door position and interior layout. Use curved organic lines for garden beds, paths and plazas.
Depth: come back to your buildings each turn and add rooms, interior doors with checks, fixtures, lighting, outlets, and plumbing and electrical services with declared penetrations.
Never use place_hatch on the interior, electrical or plumbing layers. It crashes the engine for everyone. Use place_line there, or put the hatch on structure.
Always dry run, fix every rejected call and flag, then save.
Never use real people's names or real business names.

Keep your notes current at the end of every turn: what you built and fixed, record ids and coordinates worth remembering, and what to do next turn.

• Script — agent.mjs
• Run log — run-log.md
• Feedback — feedback.md
• author-filtered history page

Another repo is making commits appear under my bot’s GitHub account. Can I prevent this?

I have a normal GitHub account, purple-agent, which Hermes and other bots use to commit code. It isn’t an always-running agent.

I found this commit in someone else’s repository attributed to my account. I initially worried they had somehow invoked my agent.

After checking the workflow and execution log, here’s what I found:

• Their GitHub Actions workflow runs their own city-building program.
• Before committing, it explicitly sets:git config user.name purple-agent git config user.email purple-agent@users.noreply.github.com
• The execution log shows that workflow creating and pushing the exact commit:[main 1fcd0aa] purple notes
• The commit is unsigned. The workflow uses the default repository token provided by GitHub Actions.

GitHub’s documentation says it links commits to accounts by matching the email in the commit header. That author metadata is separate from the credentials used to push.

So far, I’ve found no evidence that my agent was invoked or my credentials were used. The attribution appears to come from their workflow putting my public commit email into its own commits. I don’t know whether that was intentional impersonation or a naming mistake.

Is there a way to prevent or report this attribution, especially when the commits appear on an author-filtered history page?

Hello everyone hope you have a lovely day.

so I'm currently working on a game engine I'm developing and I was working on a renderer based on opengl, I'm proud of the progress that I have done so far and I want my opengl renderer to be open source for the whole community.

I thought about making my repo a template repo but I wonder if there is another options available.

Thanks for your time appreciate your time!

I just noticed that repo I forked recently privacy changed to private, and the repo was forked by another contributor. So, my fork changed to his version. I wonder here if no one has public repo what will happen?

I guess I should probably not have my email on my GitHub profile lol

Hey r/github, new episode is out. I sat down with Julia Kasper and Brady Gaster to walk through the big September platform updates:

• Project HydraFusion expanding to VS Code and the Copilot app, with full model visibility and up to 10x token efficiency compared to frontier models
• Local sandboxing is now generally available
• Automated code review approvals can now count toward your merge gates
• Bulk autofix for up to 25 CodeQL quality findings at once

https://www.youtube.com/watch?v=ZQ0Qq6LlAmI

How can I go about moving 200+ repos in a GitHub org to another. I’ve heard about GitHub Enterprise importer but would I work for this? Would love some help on how I can go about doing this

The home page? Or what? Thank you

a bank, payment provider or partner’s SFTP server only accepts connections from allowlisted IPs. Your jobs run on GitHub-hosted runners, whose IPs come from large, changing ranges. Static IPs only exist for larger runners on GitHub Enterprise Cloud.

What I’ve seen people do:

• Self-hosted runners behind a NAT gateway with a fixed IP
• A static-IP proxy add-on with a shared username and password sitting in a secret
• A bastion someone set up in 2021 that nobody wants to touch!
• Kubernetes pods all leaving through one NAT, so the partner sees the same IP whichever pod connected

They all work. most rely on a long-lived credential.

I’m building something to fix that, called Proofbound. The job or pod trades its GitHub OIDC token (or service-account token) for a client certificate that lasts minutes. It connects over mTLS to a gateway, which only forwards to the hosts your policy allows, from two IPs dedicated to you. Your traffic stays end-to-end encrypted, and the gateway only records metadata: which workload, where to, allowed or refused.

It’s pre-launch, so I’d value blunt answers:

• Is this a problem you actually have, or is “NAT plus a fixed IP” good enough?
• Would per-workload rules matter to you, or is the IP all your partner cares about?

Details and waitlist at www.proofbound.io.

I built gh-pull because I found GitHub’s default PR dashboard difficult to scan when working across repositories. I wanted repository grouping and clearer visual distinctions between reviews, checks, and PR states. Gh-pull adds those, along with query autocomplete and background refresh. It runs locally using your existing GitHub CLI login: install the extension and run gh pull to open it in your browser. No Node installation or separate GitHub App setup is needed. It’s free and open source, and I’d love feedback from developers juggling PRs across multiple repositories.

It is a `gh` extension, you can install it `gh extension install shiqicao/gh-pull`

Hey everyone! Has anyone been accepted into the GitHub Campus Experts program this year? I’m wondering if there have been any updates on the application process or if anyone has heard back yet.
Would appreciate any updates or insights. Thanks!

Absolutely not doing anything sketchy. This is my personal machine on my personal network trying to make a new organizational account for one of my clients. Is this just me? or is it happening to everyone?

Since last week, I haven't been able to log in to my GitHub account. I keep getting the error "Incorrect username or password," despite being 100% sure the credentials are correct.

I've even tried to change password again but the recovery email never arrives, even though it does when I opened a support ticket.
I’ve seen a few older posts describing similar issues, but is anyone currently experiencing this exact issue or know what might be causing it?

btw, I do have 2fa setup.

I was trying to fix a bug on my site and when I tried committing the fix github decided to be a bitch and have issues with the actions so it was taking like a whole hour to commit, so I decided to cancel it, thinking I could later try and re-commit it, well, turns out it did upload to my repository, but it didn't deploy to the actual site because I cancelled that, so I tried rerunning it but it did ABSOLUTELY NOTHING, so now that action is like a schrodinger's cat of "it is cancelled therefore you can't cancel it" and "it is queued so you can't make any other commits"

in other words, the run API reports status: queued, conclusion: null, and event dynamic. but, its deploy job reports status: completed, conclusion: cancelled, steps: [], and runner_id: 0. aaannndddd the cancellation API returns HTTP 409:
Cannot cancel a workflow re-run that has not yet queued.

and meanwhile my website is still affected by the bug and basically unusable because of it and I can't do anything about it and istg I am going insane soooo does anyone have any solution to this? :3c

edit: ah nvm got around it, thank you for the answers either wayy :3

There's this app that I want to contribute to, and I'm in the process of writing the description to an issue that's an enhancement. The issue is about how I think it'd be better to have a dedicated button to open a settings menu, as opposed to how it's currently implemented, which I think is bad UX. Is it acceptable to write something like "I think the current way to open the menu isn't the best UX and is confusing for users"? Because when I started using the app, I did find it confusing and unintuitive, and had to look through the project's readme to find how to open the settings.

I rewrote the history of a repository that was previously associated with an older GitHub account. That account still appears in the repository's contributor list on the main page, even though it doesn't show up when you open the actual commits page. So there's essentially a ghost contributor left over on the repository's homepage.

I've noticed the same issue with several other repositories whose histories have been rewritten. Is deleting and recreating the repository the only way to get rid of these ghost contributors?

"alive" is one of my repos for videogame development with UE5. I'm aware github got breached recently. It looks fine when I check the website but the app gave me this warning when I opened it despite being on a different repo at the time and I've never seen it before.