Conversation
This branch has not been deployed
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
1 participant
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.
Prevent
nbdev-newfrom copying repository metadata from a parent Git repository.I encountered this because my fastws workspace is versioned with Git. Creating an nbdev project inside that workspace caused
nbdev-newto use the workspace repository’s name, owner, branch, description, and other metadata for the new project.nbdev_create_confignow uses Git repository metadata only when the configuration target is the root of that repository. Otherwise, it uses the explicit arguments, user configuration, and target directory name as before.A workaround is to run
git initin the new project directory before runningnbdev-new. This creates a separate Git root, but project creation should work correctly without that extra step.