DEVOPS

Track weekly bundle-size drift on main and alert on creep

On a weekly schedule, measures the production bundle on the main branch, appends the data point to a BigQuery trend table.

CategoryDevOps
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionBuild main and measure bundle sizeShell
  • ActionAppend measurement to BigQuery trend tableGoogle BigQueryBigQuery
  • LogicCompute creep vs rolling 8-week average
  • OutputPost trend report to SlackSlack

What it does

Merge gates catch big jumps but miss the slow leak: dozens of PRs each adding a few kilobytes. This flow records the main-branch bundle size every week into a time-series table and reports the trend, so a 30% creep over a quarter becomes visible long before it hurts.

When to use it

Use it alongside a per-PR gate when you want a longitudinal view of bundle health. It's the dashboard-feeding companion that answers "are we getting heavier over time?" without anyone manually checking.

How it works

  1. 1A weekly schedule trigger fires (for example, Monday morning).
  2. 2A shell step checks out main, builds, and captures the gzipped bundle size plus the per-chunk breakdown.
  3. 3An action appends the measurement as a row in a BigQuery trend table keyed by date and commit SHA.
  4. 4A logic step compares this week against the rolling 8-week average to compute creep percentage.
  5. 5A Slack message posts the trend, the week-over-week delta, and a callout if creep exceeds the warning band.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ShellRun sandboxed commands inside the workspace.
  2. 2
    Connect BigQueryDatasets, queries, schemas.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.