yml1 KB

GitHub Actions Expression and Function Coverage

An 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.

Config testing Config parsing Editor testing

Preview — first 32 linesyml

# Expression-dense on purpose: a template engine has to resolve nested ${{ }} interpolation,
# the operator set, and the built-in functions before any schema check is meaningful.
name: Expression coverage

on: [push]

permissions:
  contents: read

jobs:
  compute:
    runs-on: ubuntu-latest
    if: >-
      github.event_name == 'push' &&
      !contains(github.event.head_commit.message, '[skip ci]')
    strategy:
      matrix:
        target: ${{ fromJSON('["linux", "darwin", "windows"]') }}
    env:
      CACHE_KEY: ${{ runner.os }}-${{ hashFiles('**/package-lock.json') }}
      LABEL: ${{ format('{0}/{1}@{2}', github.repository_owner, matrix.target, github.sha) }}
    steps:
      - uses: actions/checkout@v4
      - name: Conditional step
        if: matrix.target != 'windows' && success()
        run: echo "${{ join(fromJSON('["a","b"]'), '-') }}"
      - name: Always runs
        if: ${{ always() }}
        run: echo "${{ toJSON(matrix) }}"
      - name: Ternary-by-coalescing
        run: echo "${{ matrix.target == 'linux' && 'gnu' || 'other' }}"

Specifications

System: GitHub Actions
Focus: expression language
Functions: fromJSON, hashFiles, format, join, toJSON, contains, always, success
Matrix From Json: true

Testing contract

Expected to pass

Scenario: Resolve a workflow's expression language, including a matrix axis produced by fromJSON
Expected result: Every ${{ }} expression resolves without an unknown-function error and the matrix axis expands to three targets

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 Expression and Function Coverage” 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 · 1,068 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("expressions-and-contexts.yml") as f:
    data = yaml.safe_load(f)
print(data)

Generated by generation/pipelines.py. Free for any use, no attribution required — license.