agentleFS
apacheapache/airflow/.github/AGENTS.md

airflow

AGENTS.md47k starsChanged 2 days agoApache-2.0View on GitHub

breeze ci approve-workflow-runs (run by workflows/auto-approve-workflow-runs.yml) decides whether to approve an external contributor's CI runs from an estimate of the job-minutes they take. The numbers live in dev/breeze/src/airflowbreeze/utils/ciminutes_estimate.py and are medians measured on recent Tests (AMD) PR runs on public runners. After you change the CI workflows in a way that adds, removes, splits or resizes jobs (new test groups, a changed matrix, new composite workflows, a move between runner types), refresh the estimates once the change has run on…

We split this AGENTS.md into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After you change the CI workflows in a way that adds, removes, splits or resizes jobs (new test groups, a changed matrix, new composite …

    line 22
  2. Very specific:

    When you add a new job group to the workflows, add a matching group to both ci_minutes_estimate.py (with the selective-check output that …

    line 31
  3. Very specific:

    Run uv run --project dev/breeze pytest dev/breeze/tests/test_ci_minutes_estimate.py dev/breeze/tests/test_workflow_run_approval.py -xvs.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md
<!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --><!-- START doctoc generated TOC please keep comment here to allow auto update --><!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->

Table of Contents generated with DocToc

  • The .github folder — Agent Instructions
    • Keep the CI-minutes estimates in sync with the workflows
<!-- END doctoc generated TOC please keep comment here to allow auto update -->

The .github folder — Agent Instructions

Keep the CI-minutes estimates in sync with the workflows

breeze ci approve-workflow-runs (run by workflows/auto-approve-workflow-runs.yml) decides whether to approve an external contributor's CI runs from an estimate of the job-minutes they take. The numbers live in dev/breeze/src/airflow_breeze/utils/ci_minutes_estimate.py and are medians measured on recent Tests (AMD) PR runs on public runners.

After you change the CI workflows in a way that adds, removes, splits or resizes jobs (new test groups, a changed matrix, new composite workflows, a move between runner types), refresh the estimates once the change has run on enough PRs, and in any case about once a month:

  1. Run uv run dev/calibrate_ci_minutes_estimates.py --since <date> from the repository root with an authenticated gh CLI. Pick a date that covers at least a week of runs after the workflow change.
  2. Copy the medians and fits it prints into the constants of ci_minutes_estimate.py, and update the "Last calibrated" line next to them.
  3. When you add a new job group to the workflows, add a matching group to both ci_minutes_estimate.py (with the selective-check output that turns it on) and the JOB_GROUPS patterns of the calibration script. Unmatched jobs fall into the base group.
  4. Run uv run --project dev/breeze pytest dev/breeze/tests/test_ci_minutes_estimate.py dev/breeze/tests/test_workflow_run_approval.py -xvs.

The estimates cover public runners only. Self-hosted (RunsOn) runners need their own set once there is enough data from them.

Download now (ZIP)

Trending

Steady talk.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 3 mentionsApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 1 mentionJul 2026: 2 mentionsAug 2026: 1 mentionSep 2026: 3 mentionsOct 2026: 1 mentionNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the apache/airflow repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about apache/airflow

The biggest 5 of 78 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 78

Talked about on Stack Overflow, YouTube, GitHub, Bluesky and Hacker News (78 times).

On Stack Overflow · 30

25 more on Stack Overflow

On YouTube · 23

18 more on YouTube

On GitHub · 16

11 more on GitHub

On Bluesky · 6

1 more on Bluesky

On Hacker News · 3

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.