Hello,
What would be the best way to use linear releases when:
- The head of
main is production (eg www.example.com)
- The head of
develop is testing/UAT/staging (eg staging.example.com)
Engineers branch from develop to their own branch per feature (eg feature/123)
Engineers squash and merge the resulting PR from the branch to develop
Then, every so often (ideally daily), a "Release PR" between main and develop is created then merged.
Therefore a "release" will contain multiple commits eg:
[feat-123] Feature 123
[feat-234] Feature 234
[feat-567] Feature 567
I've read through the documentation several times, and cannot work out how best to set this up.
I think this release flow is fairly common, hence I thought an issue would be worth creating.
Thanks,
Hello,
What would be the best way to use linear releases when:
mainis production (eg www.example.com)developis testing/UAT/staging (eg staging.example.com)Engineers branch from
developto their own branch per feature (eg feature/123)Engineers squash and merge the resulting PR from the branch to
developThen, every so often (ideally daily), a "Release PR" between
mainanddevelopis created then merged.Therefore a "release" will contain multiple commits eg:
[feat-123] Feature 123
[feat-234] Feature 234
[feat-567] Feature 567
I've read through the documentation several times, and cannot work out how best to set this up.
I think this release flow is fairly common, hence I thought an issue would be worth creating.
Thanks,