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 should look into using Master as the dev branch and having a separate Stable branch we periodically merge commits into once we are 100% sure they are stable.
Edits:-
Need to look into this more. It's not as simple as changing the branch in config.php as tracking has to be setup for the remote dev branch.
The easier way to do this will probably be to have master as the production/stable branch and a separate dev branch. All PRs initially go into Dev. The demo and our own instances will run dev. Once a month we will merge dev into prod. This would let us still develop fairly quickly for the majority of the month, and hopefully catch most issues before they make it into prod.
The text was updated successfully, but these errors were encountered:
wrongecho
changed the title
Feature Request: Separate Master (dev) & Stable branches
Feature Request: Separate Master (stable) & Dev branches
Dec 18, 2024
We should look into using Master as the dev branch and having a separate Stable branch we periodically merge commits into once we are 100% sure they are stable.
Edits:-
Need to look into this more. It's not as simple as changing the branch in
config.php
as tracking has to be setup for the remote dev branch.The easier way to do this will probably be to have master as the production/stable branch and a separate dev branch. All PRs initially go into Dev. The demo and our own instances will run dev. Once a month we will merge dev into prod. This would let us still develop fairly quickly for the majority of the month, and hopefully catch most issues before they make it into prod.
The text was updated successfully, but these errors were encountered: