Add a git init step to bridgetown new command #18
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
|
LGTM 👍 |
jaredcwhite
added a commit
that referenced
this pull request
Apr 23, 2020
* Add permalink support to Prototype Pages * Add inspiration attribution to changelog * Oops, fix typo * Add Jared Moody to contributors list * Update CHANGELOG.md * Update documention regarding plugins folder * More plugins docs tweaks * Add a git init step to bridgetown new command (#18) * Add a git init step to bridgetown new command * Fix formatting errors * Update test to pass with Kramdown 2.2.1 * Refactoring Paginate for better performance * typo fix * Complete pagination hooks and caching perf tuning * Code cleanup * update changelog * Formatting improvements
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.
I'm surprised this wasn't already happening, so this PR adds a
git initstep after creating the new site folder. If the command fails (i.e. git isn't present on the system), it doesn't throw an error. Thanks to Rails' PR history for highlighting that potential gotcha. 😄Fixes #16