|
| 1 | +### PR fulfills these requirements |
| 2 | +- [ ] Commit message(s) and PR title follows the format `[fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made` ex. `fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors` |
| 3 | +- [ ] Tests for the changes have been added/updated (for bug fixes/features) |
| 4 | +- [ ] Docs have been added/updated (for bug fixes/features) |
| 5 | +- [ ] Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.) |
| 6 | +- [ ] Self-reviewed and ran all changes on a local instance (for bug fixes/features) |
| 7 | + |
| 8 | + |
| 9 | + |
| 10 | +#### Change has impacts in these area(s) |
| 11 | +_(check all that apply)_ |
| 12 | +- [ ] Product design |
| 13 | +- [ ] Frontend |
| 14 | + |
| 15 | + |
| 16 | + |
| 17 | +### Describe the reason for change |
| 18 | +_(link to issue, supportive screenshots etc.)_ |
| 19 | + |
| 20 | + |
| 21 | + |
| 22 | +#### What does this fix? |
| 23 | +_(if this is a bug fix)_ |
| 24 | + |
| 25 | + |
| 26 | + |
| 27 | +#### What is the new behavior? |
| 28 | +_(if this is a breaking or feature change)_ |
| 29 | + |
| 30 | + |
| 31 | + |
| 32 | +#### What is the current behavior? |
| 33 | +_(if this is a breaking or feature change)_ |
| 34 | + |
| 35 | + |
| 36 | + |
| 37 | +#### What libraries were added/updated? |
| 38 | +_(list all with version changes)_ |
| 39 | + |
| 40 | + |
| 41 | + |
| 42 | +#### Does this change affect performance? |
| 43 | +_(if so describe the impacts positive or negative)_ |
| 44 | + |
| 45 | + |
| 46 | + |
| 47 | +#### Does this change affect security? |
| 48 | +_(if so describe the impacts positive or negative)_ |
| 49 | + |
| 50 | + |
| 51 | + |
| 52 | +#### What alternative approaches were there? |
| 53 | +_(briefly list any if applicable)_ |
| 54 | + |
| 55 | + |
| 56 | + |
| 57 | +#### What feature flags were used to cover this change? |
| 58 | +_(briefly list any if applicable)_ |
| 59 | + |
| 60 | + |
| 61 | + |
| 62 | +### Does this PR introduce a breaking change? |
| 63 | +_(check only one)_ |
| 64 | +- [ ] Yes, and covered entirely by feature flag(s) |
| 65 | +- [ ] Yes, and covered partially by feature flag(s) |
| 66 | +- [ ] No |
| 67 | +- [ ] Not sure (briefly explain the situation below) |
| 68 | + |
| 69 | + |
| 70 | + |
| 71 | +### What level of testing was included in the change? |
| 72 | +_(check all that apply)_ |
| 73 | +- [ ] e2e |
| 74 | +- [ ] integration |
| 75 | +- [ ] unit |
| 76 | + |
| 77 | + |
| 78 | + |
| 79 | +### Which logical domain(s) does this change affect? |
| 80 | +_(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)_ |
0 commit comments