Skip to content

MD files only optimization only on PUSH#65181

Merged
potiuk merged 1 commit intomainfrom
md-only-optimization-only-runs-on-push
Apr 13, 2026
Merged

MD files only optimization only on PUSH#65181
potiuk merged 1 commit intomainfrom
md-only-optimization-only-runs-on-push

Conversation

@potiuk
Copy link
Copy Markdown
Member

@potiuk potiuk commented Apr 13, 2026

When we merge to v3-2-test it usually triggers full build, however
when there is only an .md file change (which happens for
AGENTS.md updates for example) - it should not trigger the
complete rebuild.


Was generative AI tooling used to co-author this PR?
  • Yes (please specify the tool below)

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

When we merge to v3-2-test it usually triggers full build, however
when there is only an .md file change (which happens for
AGENTS.md updates for example) - it should not trigger the
complete rebuild.
@potiuk potiuk force-pushed the md-only-optimization-only-runs-on-push branch from a3bc979 to 8b0bdf0 Compare April 13, 2026 22:18
@potiuk potiuk merged commit c8ebd28 into main Apr 13, 2026
37 checks passed
@potiuk potiuk deleted the md-only-optimization-only-runs-on-push branch April 13, 2026 22:22
github-actions bot pushed a commit that referenced this pull request Apr 13, 2026
When we merge to v3-2-test it usually triggers full build, however
when there is only an .md file change (which happens for
AGENTS.md updates for example) - it should not trigger the
complete rebuild.
(cherry picked from commit c8ebd28)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
@github-actions
Copy link
Copy Markdown
Contributor

Backport successfully created: v3-2-test

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status Branch Result
v3-2-test PR Link

potiuk added a commit that referenced this pull request Apr 13, 2026
When we merge to v3-2-test it usually triggers full build, however
when there is only an .md file change (which happens for
AGENTS.md updates for example) - it should not trigger the
complete rebuild.
(cherry picked from commit c8ebd28)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001 pushed a commit that referenced this pull request Apr 15, 2026
When we merge to v3-2-test it usually triggers full build, however
when there is only an .md file change (which happens for
AGENTS.md updates for example) - it should not trigger the
complete rebuild.
(cherry picked from commit c8ebd28)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001 pushed a commit that referenced this pull request Apr 15, 2026
When we merge to v3-2-test it usually triggers full build, however
when there is only an .md file change (which happens for
AGENTS.md updates for example) - it should not trigger the
complete rebuild.
(cherry picked from commit c8ebd28)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001 pushed a commit that referenced this pull request Apr 15, 2026
When we merge to v3-2-test it usually triggers full build, however
when there is only an .md file change (which happens for
AGENTS.md updates for example) - it should not trigger the
complete rebuild.
(cherry picked from commit c8ebd28)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
vatsrahul1001 pushed a commit that referenced this pull request Apr 15, 2026
When we merge to v3-2-test it usually triggers full build, however
when there is only an .md file change (which happens for
AGENTS.md updates for example) - it should not trigger the
complete rebuild.
(cherry picked from commit c8ebd28)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:dev-tools backport-to-v3-2-test Mark PR with this label to backport to v3-2-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants