feat(repository): add feature-branch publish strategy#486
Open
ZJvandeWeg wants to merge 1 commit into
Open
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.
Contributor
|
@ZJvandeWeg is attempting to deploy a commit to the Nuxt Team on Vercel. A member of the Team first needs to authorize it. |
Collaborator
|
Did you test this on both git providers? |
Author
|
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? |
Author
|
Ah, I see #474. That's one way to fix the issue. I think that's the wrong fix though. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.