You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently put all changes to the develop branch, merge the changes we want into main, create a tag on main, and then merge that back into develop. Since we are making use of squash-commits, each commit to develop is a discrete feature, and ALL commits are approved by at least one person, I'd propose that we just create tags off of develop. This way we could make our process one step as oppose to four highly redundant steps.
The text was updated successfully, but these errors were encountered:
## Fixes issue
#1030
## Description of Changes
Previously a push on the main branch triggered a deploy to prod. In the
future, creating a release will trigger that push.
The change is already built in a way that we can delete the main branch
and rename the develop branch to main as a next step (once we confirmed
everything works).
What issue are you seeing?
We currently put all changes to the
develop
branch, merge the changes we want intomain
, create a tag onmain
, and then merge that back intodevelop
. Since we are making use of squash-commits, each commit todevelop
is a discrete feature, and ALL commits are approved by at least one person, I'd propose that we just create tags off ofdevelop
. This way we could make our process one step as oppose to four highly redundant steps.The text was updated successfully, but these errors were encountered: