Skip to content

CI Scheduled fork upstream ensurance#1879

Merged
rekram1-node merged 3 commits into
anomalyco:devfrom
Ardakilic:chore/ci-fork-ensurance
May 28, 2026
Merged

CI Scheduled fork upstream ensurance#1879
rekram1-node merged 3 commits into
anomalyco:devfrom
Ardakilic:chore/ci-fork-ensurance

Conversation

@Ardakilic
Copy link
Copy Markdown
Contributor

@Ardakilic Ardakilic commented May 28, 2026

Problem

Forks of this repository inherit the same GitHub Actions workflows, including the hourly cron schedule on sync-models.yml. Every hour, each fork (currently 1k forks available) spins up runners and attempts to run the full model sync pipeline: A massive and unnecessary waste of CI resources, with missing CI secrets. It currently generates a ton of failing pipelines for every fork.

Every person who forked the repository will start to get hourly failing CI notification and mail as well, due to missing repository secrets.

People could go into their fork's Settings → Actions and disable them, but nobody does.

Changes

Added if: github.repository == 'anomalyco/models.dev' to:

  • .github/workflows/sync-models.yml — both providers and sync jobs (scheduled cron, the main offender)
  • .github/workflows/deploy.yml — the deploy job (push-triggered, but also runs on rebases/force-pushes to dev in forks, wasting runners)

This ensures these workflows only execute on the upstream repository.

Reasoning

  • Prevent recurring Action runs on every fork
  • Reduce wasted GitHub Actions minutes across the ecosystem
  • Eliminate hourly failing CI notifications for fork maintainers
  • More polite to the community members who fork the repo

@Ardakilic Ardakilic changed the title CI Schedlued fork ensurance CI Schedlued fork upstream ensurance May 28, 2026
@Ardakilic Ardakilic changed the title CI Schedlued fork upstream ensurance CI Scheduled fork upstream ensurance May 28, 2026
@rekram1-node rekram1-node merged commit acc3126 into anomalyco:dev May 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants