cal.com
cal.com copied to clipboard
calcom
chore: Identify and Split Large Code Files
What does this PR do?
this PR Identify and Split Large Code Files
Fixes #12559
- [] Bug fix (non-breaking change which fixes an issue)
- [ ] Chore (refactoring code, technical debt, workflow improvements)
- [X] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [X] Tests (Unit/Integration/E2E or any other test)
- [ ] This change requires a documentation update
How should this be tested?
- Are there environment variables that should be set?
- What are the minimal test data to have?
- What is expected (happy path) to have (input and output)?
- Any other important info that could help to test that PR
Mandatory Tasks
- [X] Make sure you have self-reviewed the code. A decent size PR without self-review might be rejected.
Checklist
@Shyam-Raghuwanshi is attempting to deploy a commit to the cal Team on Vercel.
A member of the Team first needs to authorize it.
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
Thank you for following the naming conventions! 🙏 Feel free to join our discord and post your PR link.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
hey @Shyam-Raghuwanshi whats missing here to leave draft? Also there are 2 merge conflicts. Can you investigate?
Hi @PeerRich, I am working on resolving this issue and would like to confirm if I am on the right track. I have created a draft pull request (PR).
Hi @PeerRich, I am working on resolving this issue and would like to confirm if I am on the right track. I have created a draft pull request (PR).
Hi @Shyam-Raghuwanshi looking great so far - there are some merge conflicts that are present if you get a change could you please fix them?
If you dont i have time - i will take over this PR in a few days to get this work over the line. Great job
Dear @sean-brydon, I hope this message finds you well. I wanted to inform you that I am currently engaged in another GSOC project and am unable to address the conflict at the moment. I appreciate your understanding and would be grateful if you could kindly resolve the conflict. Thank you for your cooperation.
Dear @sean-brydon, I hope this message finds you well. I wanted to inform you that I am currently engaged in another GSOC project and am unable to address the conflict at the moment. I appreciate your understanding and would be grateful if you could kindly resolve the conflict. Thank you for your cooperation.
No worries at all! Thanks for your contribution.