You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although this template is rather minimalist, a user creating a new project might want to spend a few minutes at the very beginning trimming it down further. Let's make a file (e.g. docs/ideas-for-trimming.md) which contains suggestions for such trimming. Some ideas it could include:
disable pylint (and possibly black) early on in a project's development; re-enable it later once development matures a bit
remove qiskit from requirements.txt if the project does not depend on qiskit
remove docs/images/logo.png
remove ideas-for-trimming.md itself and any other files which are specific to the template
The text was updated successfully, but these errors were encountered:
garrison
changed the title
Add suggestions for "trimming" a new project based on this template
Add suggestions for customizing a new project based on this template
Feb 21, 2022
I've broadened this issue to include all aspects of customization when the initial project is created. Before trimming, one should typically run git grep (or even a platform-independent sed invocation) to identify links and identifiers that should be updated, and also move some files to their intended destinations (e.g. the prototype_template directory).
What is the expected enhancement?
Although this template is rather minimalist, a user creating a new project might want to spend a few minutes at the very beginning trimming it down further. Let's make a file (e.g.
docs/ideas-for-trimming.md
) which contains suggestions for such trimming. Some ideas it could include:docs/images/logo.png
ideas-for-trimming.md
itself and any other files which are specific to the templateThe text was updated successfully, but these errors were encountered: