Create Issue Templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,58 @@
+---
+name: Bug report
+about: Report a bug or unexpected behavior.
+labels: [bug]
+---
+
+_Please remove any sensitive information (e.g., passwords, API keys) from your submission.
+Please check the relevant boxes and fill in the specific versions or details for the relevant items.
+Thank you for taking the time to report this issue. We will respond as soon as possible._
+
+## Description
+A clear and concise description of the bug.
+
+## Expected behavior
+What did you expect to happen when you encountered the issue?
+
+## How to reproduce
+Please provide (if available):
+- WarpX inputs files
+- PICMI Python files
+- Python post-processing scripts
+
+If you are unable to provide certain files or scripts, please describe the steps you took to encounter the issue.
+
+Please minimize your inputs/scripts to be concise and focused on the issue.
+For instance, make the simulation scripts as small and fast to run as possible.
+
+## System information
+Please check all relevant boxes and provide details.
+
+- Operating system (name and version):
+  - [ ] Linux: e.g., Ubuntu 22.04 LTS
+  - [ ] macOS: e.g., macOS Monterey 12.4
+  - [ ] Windows: e.g., Windows 11 Pro
+- Version of WarpX: e.g., latest, 24.10, etc.
+- Installation method:
+  - [ ] Conda
+  - [ ] Spack
+  - [ ] PyPI
+  - [ ] Brew
+  - [ ] From source with CMake
+  - [ ] Module system on an HPC cluster
+- Other dependencies: yes/no, describe
+- Computational resources:
+  - [ ] MPI: e.g., 2 MPI processes
+  - [ ] OpenMP: e.g., 2 OpenMP threads
+  - [ ] CPU: e.g., 2 CPUs
+  - [ ] GPU: e.g., 2 GPUs (NVIDIA, AMD, etc.)
+
+If you encountered the issue on an HPC cluster, please check our [HPC documentation](https://warpx.readthedocs.io/en/latest/install/hpc.html) to see if your HPC cluster is already supported.
+
+## Steps taken so far
+What troubleshooting steps have you taken so far, and what were the results?
+
+Have you tried compiling and running in debug mode, following the instructions in our [debugging documentation](https://warpx.readthedocs.io/en/latest/usage/workflows/debugging.html)?
+
+## Additional information
+If applicable, please add any additional information that may help explain the issue, such as log files (e.g., build logs, error logs, etc.), error messages (e.g., compiler errors, runtime errors, etc.), screenshots, or other relevant details.

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: true

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,27 @@
+---
+name: Feature request
+about: Suggest a new feature or enhancement.
+labels: [enhancement]
+---
+
+_Please remove any sensitive information (e.g., passwords, API keys) from your submission.
+Please check the relevant boxes and fill in the specific versions or details for the relevant items.
+Thank you for taking the time to report this issue. We will respond as soon as possible._
+
+## Context and motivation
+Please provide a clear and concise description of the context that is prompting you to request a new feature. What problem are you trying to solve, and how will this feature help you achieve your goals?
+
+## Proposed feature
+Describe the feature you would like to add to WarpX in detail. Please include:
+- A clear and concise description of the feature
+- Any relevant technical requirements or specifications
+- How you envision the feature being used
+
+## Alternative solutions
+Have you considered any alternative solutions or features that could achieve the same goal? If so, please describe them and explain why you believe the proposed feature is the best solution.
+
+## Additional information
+If applicable, please provide any additional information that may be relevant to the feature request, such as:
+- Links to existing codes or implementations
+- References to relevant publications or research
+- Any specific use cases or scenarios where the feature would be particularly useful

.github/ISSUE_TEMPLATE/installation-issue.md

@@ -0,0 +1,49 @@
+---
+name: Installation issue
+about: Report an issue with installing or setting up WarpX
+labels: [install]
+---
+
+_Please remove any sensitive information (e.g., passwords, API keys) from your submission.
+Please check the relevant boxes and fill in the specific versions or details for the relevant items.
+Thank you for taking the time to report this issue. We will respond as soon as possible._
+
+## Description
+A clear and concise description of the issue.
+
+## System information
+- Operating system (name and version):
+  - [ ] Linux: e.g., Ubuntu 22.04 LTS
+  - [ ] macOS: e.g., macOS Monterey 12.4
+  - [ ] Windows: e.g., Windows 11 Pro
+- Version of WarpX: e.g., latest, 24.10, etc.
+- Installation method:
+  - [ ] Conda
+  - [ ] Spack
+  - [ ] PyPI
+  - [ ] Brew
+  - [ ] From source with CMake
+  - [ ] Module system on an HPC cluster
+- Other dependencies: yes/no, describe
+- Computational resources:
+  - [ ] CPU
+  - [ ] GPU: e.g., NVIDIA, AMD, etc.
+
+If you encountered the issue on an HPC cluster, please check our [HPC documentation](https://warpx.readthedocs.io/en/latest/install/hpc.html) to see if your HPC cluster is already supported.
+
+If you encountered the issue installing from source with CMake, please provide the output of the following steps:
+1. buildsystem generation: output of `cmake --fresh -S . -B build` (include your specific build options, e.g., `-DWarpX_DIMS=3`)
+2. project build: output of `cmake --build build` (include your specific build options, e.g., `-j 4`)
+
+If applicable, please add any additional information about your software environment:
+- [ ] CMake: e.g., 3.24.0
+- [ ] C++ compiler: e.g., GNU 11.3 with NVCC 12.0.76
+- [ ] Python: e.g., CPython 3.12
+- [ ] MPI: e.g., OpenMPI 4.1.1
+- [ ] FFTW: e.g., 3.3.10
+- [ ] HDF5: e.g., 1.14.0
+- [ ] ADIOS2: e.g., 2.10.0
+- Other dependencies: yes/no, describe
+
+## Additional information
+If applicable, please add any additional information that may help explain the issue, such as log files (e.g., build logs, error logs, etc.), error messages (e.g., compiler errors, runtime errors, etc.), screenshots, or other relevant details.