Improve --no-input documentation
#1543
Labels
documentation
This issue/PR relates to or includes documentation.
good first issue
issues and pull requests for new contributors
Comments
glumia
added
the
documentation
simobasso
added
the
good first issue
|
Hi there, was looking at starting to contribute and thought this would be a good issue with which to begin. However, I see that in HISTORY.md there is an accreditation to @pokoli for their documentation on this flag. Is this issue still valid? |
|
Hi @jeremyswerdlow, yes it is still valid! If you take a look at #701 you can see that it doesn't explain exactly what happens when you provide the |
|
Great! If it's alright I'll take over this issue then! |
jeremyswerdlow
added a commit
to jeremyswerdlow/cookiecutter
that referenced
this issue
Aug 6, 2021
jeremyswerdlow
added a commit
to jeremyswerdlow/cookiecutter
that referenced
this issue
Aug 6, 2021
|
Looks like the CR needs to be approved for testing by a maintainer, if someone has a chance |
glumia
pushed a commit
to jeremyswerdlow/cookiecutter
that referenced
this issue
Oct 26, 2021
insspb
added a commit
that referenced
this issue
Jun 6, 2022
Expand cli documentation relating to the no-input flag (#1543)
|
@jeremyswerdlow @glumia Thank you for contribution, will be in next release. |
This was referenced Sep 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Check #1201 (comment).
Currently it isn't clear from the documentation what exactly cookiecutter's behaviour is in case the
--no-inputflag is provided.We should add the information about template's cache refresh and check if there's something else missing (by looking at what happens when
no_inputisTruein the source code).The text was updated successfully, but these errors were encountered: