38 lines
1.6 KiB
Markdown
38 lines
1.6 KiB
Markdown
## What does this PR do?
|
|
|
|
<!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. -->
|
|
|
|
Fixes # (issue)
|
|
|
|
<!-- Please provide a loom video for visual changes to speed up reviews -->
|
|
Loom Video: https://www.loom.com/
|
|
|
|
## Type of change
|
|
|
|
<!-- Please delete options that are not relevant. -->
|
|
|
|
- [ ] Bug fix (non-breaking change which fixes an issue)
|
|
- [ ] New feature (non-breaking change which adds functionality)
|
|
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
|
|
- [ ] This change requires a documentation update
|
|
|
|
## How should this be tested?
|
|
|
|
<!-- Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration -->
|
|
|
|
- [ ] Test A
|
|
- [ ] Test B
|
|
|
|
## Checklist
|
|
|
|
<!-- Please remove all the irrelevant bullets to your PR -->
|
|
|
|
- I haven't read the [contributing guide](https://github.com/calcom/cal.com/blob/main/CONTRIBUTING.md)
|
|
- My code doesn't follow the style guidelines of this project
|
|
- I haven't performed a self-review of my own code and corrected any misspellings
|
|
- I haven't commented my code, particularly in hard-to-understand areas
|
|
- I haven't checked if my PR needs changes to the documentation
|
|
- I haven't checked if my changes generate no new warnings
|
|
- I haven't added tests that prove my fix is effective or that my feature works
|
|
- I haven't checked if new and existing unit tests pass locally with my changes
|