GitHub Actions Scheduled Workflow with Dispatch Inputs
A scheduled workflow with two cron entries plus a manual workflow_dispatch trigger carrying a boolean and a choice input. For testing cron parsers, trigger extraction, and input-type handling in workflow tooling.
name: Nightly maintenance
on:
schedule:
- cron: "17 2 * * *"
- cron: "17 14 * * 0"
workflow_dispatch:
inputs:
dry-run:
description: Report only, change nothing
type: boolean
default: true
scope:
description: Which caches to sweep
type: choice
default: stale
options: [stale, all]
permissions:
contents: read
actions: write
jobs:
sweep:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: echo "dry-run=${{ inputs.dry-run }} scope=${{ inputs.scope }}"
Specifications
- System
- GitHub Actions
- Cron Entries
- 2
- Dispatch Inputs
- 2
- Input Types
- boolean, choice
Testing contract
Expected to pass- Scenario
- Extract and parse the cron schedules and typed dispatch inputs from a workflow
- Expected result
- Both five-field cron expressions parse, and the two dispatch inputs report types boolean and choice with their declared defaults
What is a .yml file?
YML is an alternate file extension for YAML, a human-readable data-serialization format based on indentation, key-value mappings, and lists. The content and parsing rules are identical to .yaml; only the extension differs. It is widely used for CI and application configuration files.
How to use this file
Use an example YML file to test that config loaders treat .yml and .yaml identically, and to exercise indentation, comment, and multi-document parsing.
How to use this file for testing
“GitHub Actions Scheduled Workflow with Dispatch Inputs” is a deterministic Novus Examples fixture for Config testing, Config parsing, Editor testing. TOML, INI, YAML, .env, and dotfile configuration samples with nested sections and typed values — for testing config parsers, loaders, and environment tooling.
Documented properties for this file: YML · 577 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Pipeline and infrastructure fixtures are inert configuration: steps reference fictional images and scripts, and nothing here executes. Run your linter, schema validator, migrator, or policy engine against them, and expect the deprecated-syntax and intentionally invalid variants to be rejected.
Point your config loader at the file and assert it reads the documented sections and typed values, including any deliberately-tricky nesting or comments.
Code examples
import yaml # pip install pyyaml
with open("scheduled-cleanup.yml") as f:
data = yaml.safe_load(f)
print(data)Related files
- ymlGitHub Actions Composite Action DefinitionAn action.yml-shaped composite action definition with typed inputs, a declared output bound to a step output, and a branding block. Distinct from a workflow file, and a common blind spot in workflow linters that only understand .github/workflows.
- ymlGitHub Actions Concurrency and EnvironmentA deployment workflow exercising the blocks that governance tools care about: a concurrency group with cancel-in-progress, paths-ignore filters, a named environment with a URL, and a job timeout. All hosts are example.invalid.
- ymlGitHub Actions Deprecated Workflow CommandsA deprecated-syntax workflow: ::set-output, ::set-env and ::add-path markers, a retired runner label, and v2 action pins. Every construct here was removed from the runner, so an upgrade migrator can be scored on whether it rewrites all of them.
- ymlGitHub Actions Expression and Function CoverageAn expression-dense workflow: fromJSON-generated matrix axes, hashFiles cache keys, format and join calls, a folded multi-line if condition, and the && / || coalescing idiom that stands in for a ternary. For testing template resolvers before any schema check.
- ymlGitHub Actions Matrix Include and ExcludeThe matrix case that expanders get wrong: a 3x3 base grid, two exclude rules, and one include entry that adds a combination and an extra key. Nine minus two plus one is eight jobs, documented in the specs so an expansion can be scored exactly.
- ymlGitHub Actions Node Matrix WorkflowA GitHub Actions CI workflow with a two-axis build matrix (three Node versions across two runners), an npm cache, and a conditional artifact upload. Six matrix combinations, so a workflow linter or matrix expander has a documented answer to check against.
Generated by generation/pipelines.py. Free for any use, no attribution required — license.