feat(repository): add feature-branch publish strategy - #486
ZJvandeWeg wants to merge 1 commit into
Conversation
Add `branchStrategy: 'feature-branch'` to `studio.repository` config. When set, each publish creates a `studio/YYYY-MM-DD-HH-MM-SS` branch instead of committing directly to the configured branch, enabling a PR-based review workflow for content changes.
|
@ZJvandeWeg is attempting to deploy a commit to the Nuxt Team on Vercel. A member of the Team first needs to authorize it. |
|
Did you test this on both git providers? |
|
Verifying right now with GH, and hitting a bug where the branch configured to be committed on is overridden by the branch (ref) from which is deployed. @hendrikheil I think I can fix, same PR or different one? |
|
This branch is now in production for FlowFuse: https://github.com/FlowFuse/website/blob/b37c6709ef5c4f27349c1dce79b8fc908293b48b/nuxt/package.json#L36 Note it does have a older merge base, though new changes are published on a new branch. Branch naming is slightly odd to not create conflicting names. The missing piece is the PR generation from the feature branch. It now just pushes a commit on a new branch, and the user needs to go to GH themselves. |
2 participants
At FlowFuse we use a public handbook which we want to transition to use Nuxt and Nuxt Studio for content updates. However, as a handbook is in some way the law, it needs to be approved and merged. As such, feature branches would be required.
This PR adds
branchStrategy: 'feature-branch'to thestudio.repositoryconfig. If set the publishing creates astudio/YYYY-MM-DD-HH-MM-SSbranch. The seconds are included to avoid collisions.