fix(plugin): include scope for ci.json generation #343
Conversation
This file contains 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
|
CI isn't a valid scope. The valid ones are listed here. |
colton-demetriou
changed the title
mkilpatrick
approved these changes
Jul 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Ran yext pages generate in starter and saw that the ci.json was successfully update, additionally ran npm run dev and verified that it was working on both single and multibrand repos. For multibrand repo's the commands must be:
pages generate --scope="{scope}"
pages build --scope="{scope}
Tested with this repo: https://github.com/YextSolutions/fleet-subfolder-starter
Example command: pages generate --scope="sushi.yext.com"