# Branch Per Environment Example # ## Overview ## This strategy requires a minimum of a staging branch and a production branch. The staging branch acts as an area where all the upcoming changes in the next release are aggregated. Often times the changes loaded into staging are validated and shipped out to an environment mirroring production where the team can manually test fixes and new features prior to deploying them out to production. Automate Your Release Notes in 3-Clicks @ [NextRelease.io](https://www.nextrelease.io) # Output Example # > ## Release 0.1.0 > #### Enhancements > - Enhanced Dashboard Filtering [#156](https://github.com/nextreleaseio/frontend/pull/156) ( [donaldwasserman](https://github.com/donaldwasserman) ) > > #### Bugfixes > - Resolved billing [#155](https://github.com/nextreleaseio/frontend/pull/155) ( [donaldwasserman](https://github.com/donaldwasserman) ) > - Responsive Styling Fixes [#154](https://github.com/nextreleaseio/frontend/pull/154) ( [donaldwasserman](https://github.com/donaldwasserman) ) > - Changed filtering to modified date [#152](https://github.com/nextreleaseio/frontend/pull/152) ( [donaldwasserman](https://github.com/donaldwasserman) ) # Other Examples * [GitHub Automatic PR Release Note Integration](https://github.com/nextreleaseio/example-branch-per-environment/pull/5) * [Automatic Git Tagging & GitHub Release Creation](https://github.com/nextreleaseio/example-branch-per-environment/releases)