Pushing to master branch for me triggers a build process so I always build on develop or a feature branch even on my solo projects.
Do you use your develop branch for all new feature work? Or do you create a new branch for each new feature?
I try to always make a branch to work off then merge to Develop and then to Master.
I do this because it's similar to the flow I use in teams. I also like making release snapshots in case I need to roll back what is in production.
Also, thanks to my new handy git function, I really like typing g donep and watch my merge and branch cleanup happen all by itself...quite satisfying.
g donep
Thatโs a really cool function. I will have to try that out and see if it can help me with my workflow. Thanks!
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Pushing to master branch for me triggers a build process so I always build on develop or a feature branch even on my solo projects.
Do you use your develop branch for all new feature work? Or do you create a new branch for each new feature?
I try to always make a branch to work off then merge to Develop and then to Master.
I do this because it's similar to the flow I use in teams. I also like making release snapshots in case I need to roll back what is in production.
Also, thanks to my new handy git function, I really like typing
g donepand watch my merge and branch cleanup happen all by itself...quite satisfying.๐ฎ Git 'r done when you're done.
Stephen E. Chiang ใป Aug 27 ใป 2 min read
Thatโs a really cool function. I will have to try that out and see if it can help me with my workflow. Thanks!