Making all pull requests against a single “master” branch is an excellent strategy to quickly get up and running while reducing the cognitive overhead for developers and managers. This ease of use makes a single branch release strategy popular among open source developers and projects who have simple deployment needs.
This release strategy centers around a single master branch where all of the edits from the contributors is staged. Forks, branches, and direct commits all funnel into this primary branch and then the maintainers determine when to cut a new release and push it out to their end-users.
Automate Your Release Notes in 3-Clicks @ NextRelease.io
- Enhanced Dashboard Filtering #156 ( donaldwasserman )
- Resolved billing #155 ( donaldwasserman )
- Responsive Styling Fixes #154 ( donaldwasserman )
- Changed filtering to modified date #152 ( donaldwasserman )