31–40 of 133 posts
1. Announce price increase generating bad publicity. 2. Kill bad publicity with blog pretending to be understanding and taking on feedback while "pausing" the increase. 3. Implement price increase a few months later when the bad publicity wave is over, and its old news so wont generate new headlines.
Oh good, I can postpone my migration for personal projects.
1. Announce price increase generating bad publicity. 2. Kill bad publicity with blog pretending to be understanding and taking on feedback while "pausing" the increase. 3. Implement price increase a few months later when the bad publicity wave is over, and its old news so wont generate new headlines.
> GitHub stated that it has canceled the price increase after reviewing developer feedback. It added that it will take time to listen to customers and partners. I get the feeling they got the feedback that their runners are not as indispensable to developers as they thought and realized they would lose a significant amount of users. Now if only they would listen to the feedback about windows 11 and their forced copil…
I've already jumped ship. Switching source control host was actually pretty easy. Builds still working just fine.
Losing free Actions doesn't particularly bother me, and I have no issue with paying what is most likely a negligible amount, but I don't really want to have a credit card on file which could be charged some unbounded amount if somebody gets into my account. I've shut down my personal AWS for similar reasons.
Is there any way of me just loading up a one-time $20? That will probably last well into 2027, and give me the peace of mind that I can just let it run. If my account's compromised, or I misconfigure something that goes wild, I am perfectly happy to write off that amount and have my incredibly-low-stakes toy projects fail to build.
1. Announce price increase generating bad publicity. 2. Kill bad publicity with blog pretending to be understanding and taking on feedback while "pausing" the increase. 3. Implement price increase a few months later when the bad publicity wave is over, and its old news so wont generate new headlines.
Nah, that doesn’t work when the substance of the change is this intense and has an actual effect on peoples’ bottom lines. If they wait a few months and try again, people will see their bills go up immediately and they’ll all get mad again. I don’t know what GH will do next, but if they try to do that, it will definitely backfire.
I fear this would be the obvious conclusion.
> GitHub stated that it has canceled the price increase after reviewing developer feedback. It added that it will take time to listen to customers and partners. I get the feeling they got the feedback that their runners are not as indispensable to developers as they thought and realized they would lose a significant amount of users. Now if only they would listen to the feedback about windows 11 and their forced copil…
Maybe half of all clients I work with use GitHub Actions for CI (the rest basically all use Jenkins), most of those using Actions use self-hosted runners for performance and security reasons, almost all of them reached out to me asking how difficult it would be to move away from GitHub Actions yet continue using GitHub.
Do you think these companies now suddenly stop wanting to move away from GitHub Actions because Microsoft suddenly changed their mind? I don't think so, probably less priority, but it will happen, because now the cat is out of the bag.
If they'd just do user research before announcing changes and not use announcements as "testing the waters", I'm sure they'd see a lot less churn. But I guess some number counting team somewhere in Microsoft figured out they'd make more money by charging people to run software on their own hardware, so maybe I'm just dreaming.
1. Announce price increase generating bad publicity. 2. Kill bad publicity with blog pretending to be understanding and taking on feedback while "pausing" the increase. 3. Implement price increase a few months later when the bad publicity wave is over, and its old news so wont generate new headlines.
Many people will switch for that kind of money.
Earlier quoted context omitted.
I've already jumped ship. Switching source control host was actually pretty easy. Builds still working just fine.
Great! Who did you jump to ?
Personally, for smaller scale projects that still require collaboration over the web, Gitea/Forgejo + Woodpecker CI has been a really simple, lightweight and easy to maintain solution.