8000 [Scheduler] Allow setting cron expression next run date timezone by danielburger1337 · Pull Request #50572 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

[Scheduler] Allow setting cron expression next run date timezone #50572

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

Merged
merged 1 commit into from
Jun 8, 2023
Merged

[Scheduler] Allow setting cron expression next run date timezone #50572

merged 1 commit into from
Jun 8, 2023

Conversation

danielburger1337
Copy link
Contributor
@danielburger1337 danielburger1337 commented Jun 6, 2023
Q A
Branch? 6.4
Bug fix? no
New feature? yes
Deprecations? no
Tickets
License MIT
Doc PR

Allow setting the timezone for the next run date derived from a cron expression.

This is my first contribution to an experimental component and therefor I am not familiar with the exact contribution guidelines.
As this component is experimental, I think it is ok to submit this PR against branch 6.3, right?

Im also not sure about the CHANGELOG.md entry I should make. Would I add this under the 6.3.1 section or where?

@danielburger1337 danielburger1337 requested a review from kbond as a code owner June 6, 2023 11:56
@carsonbot carsonbot added this to the 6.3 milestone Jun 6, 2023
@danielburger1337 danielburger1337 changed the title [Scheduler] Allow setting cronjob next run date timezone [Scheduler] Allow setting cron expression next run date timezone Jun 6, 2023
Copy link
Member
@kbond kbond left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @danielburger1337, this looks good to me.

It will need to be against 6.4 though. Experimental just means we may/can introduce BC breaks in 6.4 but other than that, the process for new features remains the same.

Could you add a simple test that proves the timezone is being used?

@kbond
Copy link
Member
kbond commented Jun 6, 2023

Im also not sure about the CHANGELOG.md entry I should make.

This would be in the Scheduler CHANGELOG.md under 6.4.

@kbond kbond modified the milestones: 6.3, 6.4 Jun 6, 2023
@danielburg
8000
er1337 danielburger1337 changed the base branch from 6.3 to 6.4 June 6, 2023 14:21
@danielburger1337
Copy link
Contributor Author

I am even worse at using git than I thought. 😒

I think the rebase worked in the end but for some reason GitHub automatically requested a review from a bunch of people.
Sorry for the notification spam!

@kbond
Copy link
Member
kbond commented Jun 6, 2023

No worries, I've seen that a lot lately with PR's being updated from 6.3 to 6.4. I don't think there's a way to avoid.

Copy link
Member
@nicolas-grekas nicolas-grekas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here is some nitpicking. Thanks for the PR.

@nicolas-grekas
Copy link
Member

Thank you @danielburger1337.

@nicolas-grekas nicolas-grekas merged commit be9ea53 into symfony:6.4 Jun 8, 2023
This was referenced Oct 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3834
4 participants
0