It gets even worse — convoluted GitHub action templates that no one can debug, attempting to impose on every newly created repository.
The projects at my company that use the complicated actions with gitflow are slower and less efficient.
When I release a service at my company I just do trunk based ,but I have to redo the GitHub actions initially to save it from itself. Over the long run it saves me a lot of time.
Comments
It gets even worse — convoluted GitHub action templates that no one can debug, attempting to impose on every newly created repository.
The projects at my company that use the complicated actions with gitflow are slower and less efficient.
When I release a service at my company I just do trunk based ,but I have to redo the GitHub actions initially to save it from itself. Over the long run it saves me a lot of time.