Conversation
Owner
|
What is the advantage of this command over just using |
Author
|
@imliam My own personal use case isn't fully realized until #12 would be merged. I have some private git repos thats aren't packages that I use for project templates. It can be a bit wordy:
I thought it made sense to split up #11 and #12, even though my ultimate goal is using them together. Also, |
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
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.
This command allows you to create a new project using cpx. We have a couple different repos for bootstrapping projects, so this makes it pretty easy to quickly scaffold a new project from them.
cpx new laravel/laravel projectorcpx new laravel/laravel:^11.0 projectcpx new craftcms/craft projectcpx new symfony/skeleton project