Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scheduling timezone fix #19418

Closed
wants to merge 6 commits into from
Closed

Scheduling timezone fix #19418

wants to merge 6 commits into from

Conversation

TusharBhatt1
Copy link
Contributor

@TusharBhatt1 TusharBhatt1 commented Feb 20, 2025

What does this PR do?

Mandatory Tasks (DO NOT REMOVE)

  • I have self-reviewed the code (A decent size PR without self-review might be rejected).
  • I have updated the developer docs in /docs if this PR makes changes that would require a documentation change. If N/A, write N/A here and check the checkbox.
  • I confirm automated tests are in place that prove my fix is effective or that my feature works.

@graphite-app graphite-app bot added the community Created by Linear-GitHub Sync label Feb 20, 2025
@CLAassistant
Copy link

CLAassistant commented Feb 20, 2025

CLA assistant check
All committers have signed the CLA.

@graphite-app graphite-app bot requested a review from a team February 20, 2025 18:07
Copy link
Contributor

github-actions bot commented Feb 20, 2025

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Scheduling timezone fix". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@keithwillcode keithwillcode added the community-interns The team responsible for reviewing, testing and shipping low/medium community PRs label Feb 20, 2025
@dosubot dosubot bot added the bookings area: bookings, availability, timezones, double booking label Feb 20, 2025
Copy link

graphite-app bot commented Feb 20, 2025

Graphite Automations

"Add consumer team as reviewer" took an action on this PR • (02/20/25)

1 reviewer was added to this PR based on Keith Williams's automation.

"Add community label" took an action on this PR • (02/20/25)

1 label was added to this PR based on Keith Williams's automation.

@TusharBhatt1
Copy link
Contributor Author

Closing this PR as the contributor has incorporated the suggested changes into their PR #19103

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bookings area: bookings, availability, timezones, double booking community Created by Linear-GitHub Sync community-interns The team responsible for reviewing, testing and shipping low/medium community PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[CAL-5127] Issues with scheduling timezone change without end time
4 participants