Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Work with an existing repo #283

Open
AllenDowney opened this issue Aug 26, 2022 · 1 comment
Open

Work with an existing repo #283

AllenDowney opened this issue Aug 26, 2022 · 1 comment
Labels

Comments

@AllenDowney
Copy link
Contributor

The current workflow assumes that the user has not created a directory for the project and does not already have a repo for it.

I think I'm not alone in preferring to create the repo on GitHub, clone it, and then run ccds. I would be good to support that.

Or at least provide instructions for how to work with an existing repo.

@pjbull
Copy link
Member

pjbull commented Aug 26, 2022

I've definitely also hit this.

Do either the --skip-if-file-exists or --overwrite-if-exists flags to the cookiecutter command (which will also work with the ccds command) make that workflow run in the way we would want?

@pjbull pjbull added the v2-bug label Aug 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants