These anti-agentic coding nut jobs are going to get themselves thrown out of the industry. STFU, some of us are working.
what “work” are you doing, you parasitic hack?
Let us git rid of it, angry GitHub users say of forced Copilot features
301–310 of 315 posts
Re: Let us git rid of it, angry GitHub users say of forced Copilot features
#302Github is my push --mirror location, nothing more. Main is a popular Gitlab instance gitgud.io, and I host my own secondary mirror. Gitlab is of course adding more AI and corpo garbage, and once they prevent disabling these "features" on community editions we'll see a fork of gitlab, probably. The assertion that github is some bustling hub of opportunity is a strange one. At best you get people more likely to contrib…
Yep, the headline on the Gitlab landing page is now “Build software, not toolchains. With native AI at every step.” I’d love to find a stripped down solution that focused on hosting code repos. I don’t think GitHub see it as their core business anymore.
I've been using Codeberg.org recently and really enjoying it, I just wish the CI situation was better, but I'll probably just host my own instead
Re: Let us git rid of it, angry GitHub users say of forced Copilot features
#303How on earth was Microsoft allowed to buy such a critical piece of tech infrastructure?
They were allowed to buy it because GitHub is not licensed with an FOSS licence. How on earth did we all settle on such a propietary piece of tech infrastructure? No wonder Microsoft bought it.
Re: Let us git rid of it, angry GitHub users say of forced Copilot features
#304I am not sure if it's just me but the Github UI has become incredibly slow. On bigger PRs, I regularly have diffs that take seconds to load. The actions also started hanging a lot more often and will run for 30 minutes stuck in some kind of loop unless they time out or I cancel them manually. This did not use to happen before or least not as frequently as now. Finally when I try to cancel the hung actions, the cancel…
> I am not sure if it's just me but the Github UI has become incredibly slow.
Making things work properly is terribly passé in this brave new world of magic nonsense-generating robots.
You see this with Google Docs, too; after about a decade of stagnation, Google _finally_ started adding a few features (basic Markdown support, say, better comments, a few other bits and pieces) around 2022... And it finally got a bit less slow. But now that seems to have come to a shuddering halt; once more Docs stagnates, but it has about a hundred Gemini buttons now! It also feels like it's getting slower and buggier again.
Re: Let us git rid of it, angry GitHub users say of forced Copilot features
#305Earlier quoted context omitted.
> I think GitHub added the “pull request” as a really useful add on to git and that really made it take off. Negative. The only thing GitHub added to the parlance is "forks" which are essentially like namespaced branches in the same repo.
How about an issue tracker that reacts to commit messages and pull requests?
Yeah, for me the most "magical" bit was when you pushed something to your fork and it would prompt you to make a pull request for it.
Re: Let us git rid of it, angry GitHub users say of forced Copilot features
#306> During Microsoft's July 30, 2025 earnings call, CEO Satya Nadella said GitHub Copilot continued to exhibit strong momentum and had reached 20 million users. Considering that they force it upon users and user cannot disable it, this sounds like a worthless metric. I get an email every month telling me that my Copilot access has been renewed for another month. I'm probably being counted amongst those 20M users. I cou…
> I get an email every month telling me that my Copilot access has been renewed for another month. I don't; any ideas what's different?
Probably their situation is similar to mine.
It's mandatory, on the orders of a senior manager who has no background in software development, for all developers in my department to have a Copilot subscription. I've never used it for anything, and I imagine it's the same for most of my colleagues(we do highly specialised embedded development with in-house custom everything - compiler, standard library, operating system, hardware), and it seems no-one is interested in whether it's used or not.
Consequently Microsoft is being paid $240 a year per person to do nothing whatsoever, which is surely a great business for them.
Re: Let us git rid of it, angry GitHub users say of forced Copilot features
#307I read this article and then looked at my Github and a few other projects and found no issues created by Copilot. As someone else has said they need to be triggered manually, so therefore it's the same sort of problem as with the Curl project bug bounty, where people would be spamming with automatically LLM generated fictional problems. In that case because there's a potential for money to be made, and in the Github…
You can hide/disable all Copilot features in VSCode.
Re: Let us git rid of it, angry GitHub users say of forced Copilot features
#308Earlier quoted context omitted.
Was GitHub really critical at time of purchase? Or has Microsoft turned it into critical infrastructure?
> Was GitHub really critical at time of purchase? Do you think they would have bought it otherwise? Same for NPM, they got bought for huge sums of money because they were "critical" already.
I am of the opinion that it wasn't critical infra, but it was at least unique infra. Similar to LinkedIn, which MS acquired. It wasn't that LI was critical it was because it was unique.
And since the acquisition, they have built it out to be critical. Similar to what META did with Instagram. Instagram wasn't critical when META purchased it, but now it is the cornerstone of any business's online presence as it has been built out.
Re: Let us git rid of it, angry GitHub users say of forced Copilot features
#309Github is my push --mirror location, nothing more. Main is a popular Gitlab instance gitgud.io, and I host my own secondary mirror. Gitlab is of course adding more AI and corpo garbage, and once they prevent disabling these "features" on community editions we'll see a fork of gitlab, probably. The assertion that github is some bustling hub of opportunity is a strange one. At best you get people more likely to contrib…
Yep, the headline on the Gitlab landing page is now “Build software, not toolchains. With native AI at every step.” I’d love to find a stripped down solution that focused on hosting code repos. I don’t think GitHub see it as their core business anymore.
My prefernce is Forgejo
Re: Let us git rid of it, angry GitHub users say of forced Copilot features
#310Earlier quoted context omitted.
AI is the first dev tool that makes a difference that is immediately noticeable even for higher layers, that's why they apply pressure. The core problem, as OP called out, is change aversion. It's just that for many previous useful changes, management couldn't immediately see the usefulness, or there would've been pressure too. Let's not forget that well-defined development processes with things like CI/CD, testing,…
Execs can suddenly reliably measure productivity? Or does AI just give them the easier to measure, short term benefits.
They certainly realize when work is significantly accelerated. They might miss that it doesn't apply to all kinds of work equally, but they see some things go multiples faster, they see the folks behind those things using AI, and they draw conclusions.