What is the general best practice for organizing an Auth0 repo that deploys using the deploy CLI? In the docs, they recommend a branch per tenant. Then, we push changes upstream from dev ending in prod.
What is the recommended way to branch off of this? Branch off of dev, merge to dev and then merge to the rest of the branches one by one? Would it be expected that there exist any “main” branch in this structure? Just looking for some best practices here
Apart from what we already share we’re not able to be more precise on the guidance here as it’s more like case by case scenario that’s why we only provide the initial guideline. Thank you!
@konrad.sopala Totally understand that this could vary greatly across users. Do you think you could define an example of a potential path from dev to prod?