e-volv

CI playbook

SeedDataRefresh

Monthly regeneration of development seed data and test fixtures from the current schema, opening a PR only when tests pass.

Monthly, regenerates development seed data and test fixtures from the current schema so fixtures do not drift behind schema changes. Detects fixtures referencing dropped fields or missing required ones, regenerates them with realistic values, runs the test suite against the new fixtures, and opens a pull request only if the tests pass.

Identifier
seed-data-refresh
Version
1.0.1
Steps
3
Triggers
1
  • seed
  • fixtures
  • schema
  • testing
  • scheduled
  • automation

When it runs

Scheduleschedule.monthly
Schedule
Day 1 of each month at 06:00 UTC 0 6 1 * *
Timezone
UTC

The pipeline

The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.

  1. 01
    Monthly Schedule (1st 06:00 UTC)trigger

    The event that starts the run.

  2. 02
    Clone Repository ⚠️ SET YOUR REPOgit.clone

    Shallow-clones the repository at the right ref.

  3. 03
    Regenerate Seed Data & Open PRagent.run

    One agent works the task with its toolkit.

The agent

Seed Data Refresher

Base type
Senior Developer
Temperature
0.2
Max iterations
50
Tools
8

Filesystem · 3

  • read_fileRead File · read
  • list_dirList Directory · read
  • write_fileWrite File · write

Git provider · 3

  • create_branchCreate Branch · write
  • create_or_update_fileCreate or Update File · write
  • create_pull_requestCreate Pull Request · write

Terminal · 1

  • run_terminal_cmdRun Terminal Command · write

Status · 1

  • update_statusUpdate Status · write