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
description: Many problems are related to a specific Copier template. If you can provide a template, please do it. It can be a Git repo URL, a .zip file containing the template, or instructions to build it.
validations:
required: true
- type: textarea
id: reproduce
attributes:
label: To Reproduce
description: Steps to reproduce the behavior.
placeholder: |
1. Run `copier ...`
2. Answer ...
3. Choose ...
4. See error
- type: textarea
id: logs
attributes:
label: Logs
description: Provide logs of the problem. These will typically happen when getting to the latest step explained above if Copier produces an error. It helps too if you paste your copying session.
render: console
- type: textarea
id: expected
attributes:
label: Expected behavior
description: A clear and concise description of what you expected to happen.
validations:
required: true
Since the issue templates are managed in this project, they are inherited by all projects in the copier-org organization. This is suboptimal for projects in this organization that aren't closely related to Copier. For instance, when somebody would like to report a problem in the jinja2-jsonschema project, Copier-specific information is presented which may be confusing.
In fact, even this issue shows that the "problem" issue template is not perfectly applicable because this issue isn't about Copier and I even need to provide some info about my runtime environment. 😆
I see two options:
We move the issue templates to the individual projects.
Describe the problem
The issue template for reporting problems contains Copier-specific information:
.github/.github/ISSUE_TEMPLATE/problem.yml
Lines 14 to 46 in aace7c2
Since the issue templates are managed in this project, they are inherited by all projects in the
copier-org
organization. This is suboptimal for projects in this organization that aren't closely related to Copier. For instance, when somebody would like to report a problem in thejinja2-jsonschema
project, Copier-specific information is presented which may be confusing.In fact, even this issue shows that the "problem" issue template is not perfectly applicable because this issue isn't about Copier and I even need to provide some info about my runtime environment. 😆
I see two options:
WDYT, @yajo?
Template
n/a
To Reproduce
No response
Logs
No response
Expected behavior
The "problem" issue template should either be generic or tailored to the respective project.
Screenshots/screencasts/logs
No response
Operating system
Linux
Operating system distribution and version
Ubuntu 20.04
Copier version
7.2.0
Python version
3.10
Installation method
pipx+pypi
Additional context
n/a
The text was updated successfully, but these errors were encountered: