Menu

Your CI is testing the wrong PR first
📰

Your CI is testing the wrong PR first

DEV Community: cicd·Daniel Schroeder·15 days ago
#X2Z8P6MX
#devtocicd#devto#dev#merge#turn
Reading 0:00
15s threshold

I maintain a handful of open source projects that deploy real infrastructure in their tests. Not mocks. An actual AWS stack gets created, poked at, torn down. Only one copy of that stack exists, so only one test run can use it at a time.

That constraint sounds manageable until you add Renovate and release-please to the repo. Suddenly there are six open pull requests on a Tuesday morning, all of them want the stack, and GitHub Actions has no opinion about who should go first. It took me an embarrassingly long time to notice how much of my CI minutes were spent testing commits that were never going to be merged in that state.

So I wrote priority-boarding , a GitHub Action that queues workflow runs, lets you order them by PR label, and knows a few things about auto-merge and outdated branches that a plain lock doesn't.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.