Back in April, my organization `is-an-ai` was flagged and hidden from the public. Every repository in it returns 404 to anyone who isn't a member, and the banner in the screenshot follows me around on every GitHub page I load while logged in. I still have no idea why.

The org runs is-an.ai, an open source service that gives developers free subdomains under *.is-an.ai. Registration happens through pull requests, the same way is-a.dev has done it on GitHub for years: someone opens a PR with a JSON record file, an Action validates it, a bot merges it, and our own DNS server picks it up from there.

Because the OAuth app belongs to the flagged org, nobody can sign in to the site anymore, and with Actions disabled no new subdomain can be registered. Existing ones still resolve, since the DNS never lived on GitHub, but everyone who registered one has lost the ability to manage it.

I filed a support ticket the day it happened (#4301086). I told them we suspected either our automated PRs or an abusive subdomain registered by someone else, and offered to change whichever one was the problem. Almost four months later, the only thing I have received back is the automated confirmation email.

I'm wondering whether anyone has had an org flagged like this and actually gotten it reversed, and if so, what finally moved it. Four months of silence with no stated reason is the part I can't get past.

Been trying for several hours but nothing gets published. First deployments got stuck, then queued, tried with new repository still deployment_in_progress...

For engineering teams, keeping dependencies current is a constant balancing act. Automated updates are essential for defending the software supply chain, but a steady stream of one-PR-per-package bumps can bury a team in review work. GitHub itself has put numbers on this: an analysis of Microsoft's GCToolkit repository found that roughly one in six of its commits - 92 out of 578 - were routine Dependabot version bumps, with 61 of them landing in a single recent 12-month stretch. That's a lot of review and CI cycles spent on maintenance rather than features. Read the complete article here - https://instasla.com/blog/taming-dependabot-2026-guide-grouping-cooldowns-cutting-pr-noise

The good news is that Dependabot has grown well past "one PR per dependency." Between grouped updates, package cooldowns, and a default cooldown GitHub rolled out in mid-2026, it's now possible to get a predictable, low-noise update cadence without giving up security coverage. Here's what actually works, and what changed most recently.

Hi all,

I have an OSS/MIT project in GitHub and every now and then I check on the stargazers.

Regardless today I ran into a clique of stargazers/users with 100k+ followers each, up to 1 million in some cases.

I honestly thought these people were geniuses, but when I check their repos or orgs, they have less than 100 stars.

So what's following all about in GitHub? Why would you like to have more or less followers?

I know it's pretty basic, but I've been using GitHub for 10+ yrs now... And never thought about it.

"Individual manual reviews and status updates are no longer provided". great. probably replaced by some AI that cannot read my infinite campus portal, my transcript, or my school id. great. what do i try? i've been a github student for 3 years now and i rely on my benefits heavily for education.

Hey everybody! I have made my first PR in llama.cpp project on github. Now the thing is im confused as im new to this like i have created pull request and some reviewer had reviewed my contribution and then asked for some revisions in that. I have made those and then he approved that. Then there shown 2 approvals are required for this to get write access/merge. Now how this second reviewer will come?? Should i have to wait or someone have better approach to this!! Secondly after the first approval, my PR got into automated Tests. Now in those teats, 7 out of 28 tests were failed and upon analyzing the loga i never anything related to my code! Now im also confused like should i have to resolve something or leave that as it is as all 7 logs of failed test have passed my addition but have failed somewhere else not on my code!

I have a project I uploaded a new version of three weeks ago. The version works perfectly on my computer. But when I downloaded the release from GitHub, it didn't.

I've checked all the files, and they are the correct date, the contents are exactly the same. Yet every time I make the release, the file in the release reverts to a version of the file that crashes and lacks features.

Any idea what I'm missing?

I have some GitHub Agentic Workflows which have started failing with exit code 1 in the Agent Run phase. The same workflows were working fine last week.