Skip to content

translation-status: the verification fixture is not in the repo #40

Description

@mairas

translation-status.yml was verified by building a two-page, one-locale
mkdocs-static-i18n tree on a throwaway branch, running it through four
scenarios, and deleting the branch. The run IDs are in
#39; Actions logs
expire after 90 days and the fixture is gone already.

The next person to touch the PATCH/POST branch, the PIPESTATUS handling or
the steps.anchors.outcome condition has no way to re-run any of it without
rebuilding the fixture by hand, so they will not.

examples/docs-repo/ is the natural home. It needs mkdocs.yml with two
locales, docs/en/ and one translation with translated_from stamps,
pyproject.toml pinning halos-docs-tools, and a README saying how to reach
each state: edit an English page for stale, remove the stamp for unstamped,
add an English page for missing, delete one for orphaned, break a fragment
for the anchor path, drop pull-requests: write for the read-only token.

Open question worth deciding first: whether to commit uv.lock with it. The
workflow runs uv sync --locked, so a fixture without one cannot be driven by
the workflow unchanged, and uv.lock for a mkdocs-material project is around
110 KB.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions