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
I've been using the develop branch for unreleased development changes, with the default master branch being reserved for the latest stable release. But I've recently concluded that this isn't really necessary and it's causing some confusion, resulting in the assumption that the master branch should be the base of all PRs.
To avoid further confusion, I'm going delete the develop branch and place all unreleased changes in the default master branch.
This shouldn't break anything, as those who wish to work with a particular version of Bloom's codebase should be using tags. For example, to work with the codebase at v1.0.0, simply checkout to the v1.0.0 tag: git checkout v1.0.0
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've been using the
develop
branch for unreleased development changes, with the defaultmaster
branch being reserved for the latest stable release. But I've recently concluded that this isn't really necessary and it's causing some confusion, resulting in the assumption that themaster
branch should be the base of all PRs.To avoid further confusion, I'm going delete the
develop
branch and place all unreleased changes in the defaultmaster
branch.This shouldn't break anything, as those who wish to work with a particular version of Bloom's codebase should be using tags. For example, to work with the codebase at v1.0.0, simply checkout to the
v1.0.0
tag:git checkout v1.0.0
Beta Was this translation helpful? Give feedback.
All reactions