Menu

1 / 5

Your CI should cut the release, not your laptop

DEV Community: github·Ian·4 days ago
#EEG22tNb
#devtogithub#technology#devto#dev#release
Reading 0:00
15s threshold

This one covers November 3 to 10. The week was about one question: can an AI agent on a throwaway cloud machine ship the way I do from my desk? Most of the answer landed in my workflow kit. The rest went into a Windows bug class in a CLI I maintain, and into a new private tool that designs shirts with exactly one language-model call.

A cloud session hit three walls on the way to a release

workkit is my workflow kit for Claude Code: GitHub issues as the work list, labels as the pipeline, hooks that enforce the rules. On my Mac, "ship" means a work commit, a release commit, a push to main, green CI, then a GitHub release.

Then I ran the same loop in a Claude Code cloud session, and it stopped halfway. It hit three walls:

The branch. The session is pinned to its own claude/<name> branch and may not push anywhere else. So the commits never reached main, and CI, which runs on pull requests and on pushes to main, never started.

GraphQL.…

Continue reading — create a free account

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