Why Tech Platforms Don't Use GitHub Actions: The Case for GitHub Apps and Centralized Runners at Scale

·1 views

Originally published at labitcode.com When a software team grows from 10 developers to 50, GitHub Actions feels like magic. You drop a .github/workflows/ci.yml file into your repository, define a few steps in YAML, and GitHub spins up an Azure-hosted virtual machine to build and test your code. There are no build servers to patch, no Jenkins masters to restart, and zero upfront infrastructure to maintain. Fast-forward to an enterprise organization with 3,000 developers, 1,200 microservices, and high-frequency deployment cadences. Suddenly, that same .github/workflows directory transforms into

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

[query-inspector] A Claude Code skill for extracting and tuning SQL/ORM queries

query-inspector is a Claude Code skill that extracts the SQL/ORM queries from your project's source, then diagnoses and tunes missing indexes / N+1 problems / anti-patterns. Queries that run fine until the data piles up. N+1 problems that sail through code review. The real SQL your ORM generates, invisible in the code. It catches all of this right before you commit, not after it reaches production.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Why I Stopped Self-Hosting AI Models (And You Probably Should Too)

I spent three months and roughly $500 on GPU hardware trying to prove a point. That point was that I could run my own AI models, free from the shackles of API pricing and vendor lock-in. I was wrong, and the journey was both humbling and expensive. This isn't just a "cloud good, self-host bad" tirade. There are legitimate reasons to self-host—privacy, data sovereignty, or just the sheer nerdery of building your own inference rig.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Wirelist: cards, divided lists and grids for Laravel and Livewire

A list of cases, tasks or properties is not a table, as each record reads as a card, and forcing it into columns leaves gaps and odd widths. Wirelist draws those lists. Records as divided rows, separate cards or a grid, each one opening its record, with a row actions menu, load more and the 11 themes of the wire* family. It is built on Wiretables, so tables and lists share their look and sit together on one screen. It requires Wiretables, which Composer installs with it.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Part 6: Building it with MuleSoft Vibes: skills, rules, workflows and hooks

Part 6 of 10 · Building an Agentic Change-Approval MVP on MuleSoft Parts 4 and 5 covered what the integration team builds: MCP tool flows with strict contracts, behind a governed gateway. This part covers how they build it. We used MuleSoft Vibes in Anypoint Code Builder, and the interesting part wasn't the code it wrote. It was how we taught it our standards so every tool came out the same way. Vibes gives you three building blocks, and each one solves a different problem: What it is When it applies What we used it for Rules Natural-language constraints Every message (global or workspace) Sta

0 comments Read more at DEV Community