Added docs about merging schedules. #64
Annotations
11 warnings
|
build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-and-test:
FluentScheduler/Cron/NCrontab-v3.4.0/CrontabSchedule.cs#L92
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
|
|
build-and-test:
FluentScheduler/Cron/NCrontab-v3.4.0/Extensions.cs#L34
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
|
|
build-and-test:
FluentScheduler/Cron/NCrontab-v3.4.0/CrontabException.cs#L35
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
|
|
build-and-test:
FluentScheduler/Cron/NCrontab-v3.4.0/CrontabException.cs#L35
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
|
|
build-and-test:
FluentScheduler/Cron/NCrontab-v3.4.0/CrontabException.cs#L32
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
|
|
build-and-test:
FluentScheduler/Cron/NCrontab-v3.4.0/CrontabField.cs#L263
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
|
|
build-and-test:
FluentScheduler/Cron/NCrontab-v3.4.0/CrontabFieldImpl.cs#L59
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
|
|
build-and-test:
FluentScheduler/Cron/NCrontab-v3.4.0/CrontabFieldImpl.cs#L46
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
|
|
build-and-test:
FluentScheduler/Cron/NCrontab-v3.4.0/CrontabFieldImpl.cs#L161
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
|
|
build-and-test:
FluentScheduler/Cron/NCrontab-v3.4.0/CrontabField.cs#L48
The annotation for nullable reference types should only be used in code within a '#nullable' annotations context. Auto-generated code requires an explicit '#nullable' directive in source.
|