You're viewing a single thread.
15 comments
Hey! Why don't you try to build a basic github action from scratch and deploy it 40 times before it's green, waiting 10 minutes between builds to discover how each task creatively interprets directory path notation!
This is so true, I use copilot for things like actions and dockerfiles so I don't feel an urge to bash my brains out more than I use it for code gen
Get out of my head! Out I say!
You'd think there'd be a better way of testing CI configs locally, like using selfhosted runners, but no, they need me to push changes to origin so that GitHub can then trigger the job on my local docker host. At least CircleCI gave us CLI to validate and partly run jobs from config files locally, ... but only partly.
15 comments