Wondeirng how y'all structure your code for a typical merge request git repo. New commits to branches should perform build and test, possibly, publish. Commits to main branch should perform build, test, publish an deploy. Also is there any way to resume a pipeline? For example gitlab supports manual input gates for progressing the pipeline where user input is required from the UI to proceed. Wondering how I'd delegate this gitlab UI action to my pipeline.
#Suggestions for organizing main branch build vs branch build
brazen fog