@ngbima
Man, this Git workflow has been frustrating me lately. Team uses main for Prod and develop for UAT. Every feature I finish, I have to manually create two branches, switch back and forth, merge, push, then open separate PRs. Today I got tired of the nonsense and just automated the whole thing. Now I run one command yarn dual-pr and it handles pulling latest, branching, merging and pushing to both. Even drops the PR links straight in terminal.If there's conflict on the develop side it stops and tells me. Super simple.Script here if you need it: gist.github.com/boluwatifee4/f… Anyone else dealing with this annoying dual env flow? How do you handle it?
0 reply
0 recast
0 reaction