Summary
We form the dev teams by business domains, for example, Order, Article, or Inventory team.
Each team consists of 1 Product Owne...
For further actions, you may consider blocking this person and/or reporting abuse
Great insight thanks for sharing.
When you pushing a deadline..throw this stuff out da window
Pure gold... Thank you for sharing ❤️
Thanks ❤️
Are you using any branch for the productive code? It looks like this is not the case, so is it correct, that a certain commit of your main branch, which is for development, contains the productive code?
Hi there!
We use the main branch for both the development and production environment. So new commits to this branch are always automatically deployed to the development env. But we only deploy specific commits to production manually.
So yea, the feature branches (branched off from the main branch) always include the latest productive code.
Amazing post, but just wondering why do you need ticket name for each feature?
Hi Munezero,
Thank you for being interested in my post!
We add the ticket name for the following reasons:
Have a nice day! :)
This is how we do it as well. Main branch and feature branches. Rather easy to maintain and do deployments. Has its pros and cons though.
how is the process to make new releases? does you make tag branches in the github?
Hi Walace,
We only use the main branch to deploy new code to Production. The team will manually choose a specific commit on this branch for deployment.