|
| 1 | +# Pull Request |
| 2 | + |
| 3 | +## Description |
| 4 | +<!-- Provide a brief description of the changes in this PR --> |
| 5 | + |
| 6 | +## Type of Change |
| 7 | +<!-- Mark the relevant option with an "x" --> |
| 8 | +- [ ] Bug fix (non-breaking change which fixes an issue) |
| 9 | +- [ ] New feature (non-breaking change which adds functionality) |
| 10 | +- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) |
| 11 | +- [ ] Documentation update |
| 12 | +- [ ] Performance improvement |
| 13 | +- [ ] Code refactoring |
| 14 | +- [ ] Test improvements |
| 15 | + |
| 16 | +## Related Issue |
| 17 | +<!-- Link to the issue this PR addresses --> |
| 18 | +Fixes #(issue number) |
| 19 | + |
| 20 | +## Changes Made |
| 21 | +<!-- Provide a detailed list of changes made --> |
| 22 | +- |
| 23 | +- |
| 24 | +- |
| 25 | + |
| 26 | +## Quantum Backends Affected |
| 27 | +<!-- Check all that apply --> |
| 28 | +- [ ] PennyLane |
| 29 | +- [ ] Qiskit |
| 30 | +- [ ] Cirq |
| 31 | +- [ ] AWS Braket |
| 32 | +- [ ] TKET |
| 33 | +- [ ] D-Wave Ocean |
| 34 | +- [ ] Backend-agnostic changes |
| 35 | +- [ ] Not applicable |
| 36 | + |
| 37 | +## Testing |
| 38 | +<!-- Describe the testing you've done --> |
| 39 | +- [ ] All existing tests pass |
| 40 | +- [ ] New tests added for new functionality |
| 41 | +- [ ] Tests cover edge cases |
| 42 | +- [ ] Manual testing performed |
| 43 | +- [ ] Integration tests updated |
| 44 | + |
| 45 | +### Test Commands Run |
| 46 | +```bash |
| 47 | +# Add the commands you used to test your changes |
| 48 | +uv run pytest |
| 49 | +``` |
| 50 | + |
| 51 | +## Performance Impact |
| 52 | +<!-- Describe any performance implications --> |
| 53 | +- [ ] No performance impact |
| 54 | +- [ ] Performance improvement |
| 55 | +- [ ] Minor performance regression (justified) |
| 56 | +- [ ] Significant performance changes (benchmarks included) |
| 57 | + |
| 58 | +## Documentation |
| 59 | +- [ ] Code is self-documenting with clear variable/function names |
| 60 | +- [ ] Docstrings added/updated for new functions |
| 61 | +- [ ] README updated if needed |
| 62 | +- [ ] Documentation website updated if needed |
| 63 | +- [ ] Examples added/updated if applicable |
| 64 | + |
| 65 | +## Code Quality |
| 66 | +- [ ] Code follows project style guidelines |
| 67 | +- [ ] `uv run ruff check .` passes |
| 68 | +- [ ] `uv run black .` applied |
| 69 | +- [ ] `uv run mypy .` passes (if applicable) |
| 70 | +- [ ] No new warnings introduced |
| 71 | + |
| 72 | +## Checklist |
| 73 | +- [ ] I have read the [contributing guidelines](../CONTRIBUTING.md) |
| 74 | +- [ ] My code follows the code style of this project |
| 75 | +- [ ] I have added tests that prove my fix is effective or that my feature works |
| 76 | +- [ ] I have added necessary documentation (if appropriate) |
| 77 | +- [ ] Any dependent changes have been merged and published |
| 78 | + |
| 79 | +## Screenshots/Outputs |
| 80 | +<!-- If applicable, add screenshots or code outputs --> |
| 81 | + |
| 82 | +## Additional Notes |
| 83 | +<!-- Any additional information that reviewers should know --> |
| 84 | + |
| 85 | +## Review Guidelines |
| 86 | +<!-- For reviewers --> |
| 87 | +- Does this change align with the project goals? |
| 88 | +- Are there any security concerns? |
| 89 | +- Is the code well-tested? |
| 90 | +- Are breaking changes properly documented? |
| 91 | +- Does this maintain backward compatibility where possible? |
0 commit comments