|
| 1 | +<!-- Thanks for sending a pull request! Here are some tips for you: |
| 2 | +
|
| 3 | +1. If this is your first time, Please carefully read the comments in our pull request template. |
| 4 | +2. Please label this pull request according to what type of issue you are addressing, especially if this is a release targeted pull request. |
| 5 | +3. Ensure you have added or ran the appropriate tests for your PR. |
| 6 | +4. If you want *faster* PR reviews, Please contact us proactively. |
| 7 | +--> |
| 8 | + |
| 9 | +#### What type of PR is this? |
| 10 | +<!-- |
| 11 | +- **feat:** new feature |
| 12 | +- **fix:** fix bug |
| 13 | +- **docs:** documentation |
| 14 | +- **style:** format(Changes that do not affect code execution) |
| 15 | +- **test:** add test codes |
| 16 | +- **chore:** changes to the build process or accessibility tools |
| 17 | +- **revert:** revoked content |
| 18 | +- **close:** close issue |
| 19 | +- **release:** release version |
| 20 | +--> |
| 21 | + |
| 22 | +#### What does this PR do? |
| 23 | +<!-- |
| 24 | +Provide a brief description of what this PR does |
| 25 | +--> |
| 26 | + |
| 27 | +#### Which issue(s) does this PR fix? |
| 28 | +<!-- |
| 29 | +Reference any relevant issue(s) by using the syntax `Fixes #<issue_number>`, If PR is about `failing-tests or flakes`, please post the related issues/tests in a comment and do not use `Fixes`_* |
| 30 | +--> |
| 31 | +Fixes # |
| 32 | +#### Special notes for your reviewer: |
| 33 | +<!-- |
| 34 | +If there's anything specific you'd like your reviewer to pay attention to, mention it here |
| 35 | +--> |
| 36 | + |
| 37 | +#### Screenshots (if applicable): |
| 38 | +<!-- |
| 39 | +Insert screenshots or gifs to demonstrate the changes, if applicable |
| 40 | +--> |
| 41 | +```release-note |
| 42 | +
|
| 43 | +``` |
| 44 | + |
| 45 | +#### Additional Comments: |
| 46 | +<!-- |
| 47 | +Any additional information or comments you'd like to include |
| 48 | +--> |
| 49 | +```release-note |
| 50 | +
|
| 51 | +``` |
0 commit comments