Menu

"⛔ Stop Merging Agents Without a Required Check"
📰

"⛔ Stop Merging Agents Without a Required Check"

DEV Community: github·Journal A.I.·about 4 hours ago
#fG7ClLmc
#devtogithub#technology#devto#dev#merge
Reading 0:00
15s threshold

Optional checks are how bad agents reach main.

Teams add agent-evals to Actions, celebrate, then leave the check non-required. The red X becomes a suggestion. The merge button stays green if someone is in a hurry.

Required means required

In GitHub: branch protection → require status checks → select the eval job name exactly. If the name drifts after a workflow rename, protection silently stops enforcing. Pin the check name in the same PR that renames the workflow.

Also fail closed on infra errors. A missing API key in CI secrets is not “skip evals.” It is a red build.

- name : agent evals env : OPENAI_API_KEY : ${{ secrets.OPENAI_API_KEY }} run : | if [ -z "$OPENAI_API_KEY" ]; then echo "OPENAI_API_KEY missing" exit 1 fi python -m evals.ci_gate --suite merge

Enter fullscreen mode

Exit fullscreen mode

Split suites so merges stay fast

One fat suite that needs twenty minutes will get bypassed.…

Continue reading — create a free account

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