|
| 1 | +<!-- |
| 2 | +Thanks for contributing to CUDA-Q Libraries! |
| 3 | +
|
| 4 | +Please read the full Pull Request Guidelines in Contributing.md: |
| 5 | +https://github.com/NVIDIA/cudaqx/blob/main/Contributing.md#pull-request-guidelines |
| 6 | +--> |
| 7 | + |
| 8 | +## Description |
| 9 | + |
| 10 | +<!-- What does this PR change, and why? Link related issues. --> |
| 11 | + |
| 12 | +## Runtime / performance impact |
| 13 | + |
| 14 | +<!-- |
| 15 | +If this change affects performance, paste benchmark numbers here. |
| 16 | +Otherwise write "N/A". |
| 17 | +--> |
| 18 | + |
| 19 | +## Self-review checklist |
| 20 | + |
| 21 | +Please confirm each item before requesting review. Check `[x]` or strike |
| 22 | +through and explain. |
| 23 | + |
| 24 | +### Before requesting review |
| 25 | +- [ ] I reviewed my own full diff in GitHub or my editor. |
| 26 | +- [ ] PR is in Draft if it is not yet ready for review. |
| 27 | +- [ ] Temporary / debugging changes have been removed. |
| 28 | +- [ ] Local test logs reviewed; no unexplained warnings or errors. |
| 29 | +- [ ] CI logs reviewed; no unexplained warnings or errors. |
| 30 | +- [ ] Full CI has been run. |
| 31 | + |
| 32 | +### Scope and size |
| 33 | +- [ ] PR is under ~1000 lines, or an exception is justified in the description. |
| 34 | +- [ ] Refactoring-only changes are isolated in their own PR(s). |
| 35 | +- [ ] No existing tests were disabled or modified just to make this PR pass |
| 36 | + (if so, an issue has been raised). |
| 37 | + |
| 38 | +### Tests |
| 39 | +- [ ] New functionality has new tests. |
| 40 | +- [ ] Tests fail if the new functionality is broken (including crashes), not |
| 41 | + just when it is missing. |
| 42 | +- [ ] Negative tests added where exceptions are expected. |
| 43 | +- [ ] Truth data added where simple `EXPECT_*` / `assert` checks are |
| 44 | + insufficient for algorithmic correctness. |
| 45 | +- [ ] CI runtime impact considered; team notified if significant. |
| 46 | + |
| 47 | +### Documentation |
| 48 | +- [ ] Public-facing APIs have Doxygen docs. |
| 49 | +- [ ] User-visible behavior changes have public docs, or a follow-up is |
| 50 | + tracked. |
| 51 | +- [ ] User-facing docs for new features are in a **separate PR** held until |
| 52 | + release (the docs site publishes immediately on merge to the default |
| 53 | + branch, so feature docs must not land before the feature ships). |
| 54 | + |
| 55 | +### Code style |
| 56 | +- [ ] Naming follows the existing convention (`snake_case` vs `camelCase`) for |
| 57 | + the area being modified. |
| 58 | + |
| 59 | +### Dependencies |
| 60 | +- [ ] No new third-party dependencies, **or** the team has been notified and |
| 61 | + OSRB tickets filed. |
0 commit comments