Repository navigation
Keep what contributors need about fork CI in the contributor docs - #77133
Merged
Merged
Conversation
potiuk
requested review from
amoghrajesh,
ashb,
bugraoz93,
choo121600,
ephraimbuddy,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl and
vatsrahul1001
as code owners
November 15, 2026 18:43
jscheffl
approved these changes
Nov 15, 2026
1 task done
The contributor docs and the fork CI design doc overlapped, and the contributor section mixed what to do with why the monitor does it, as was raised on the dev list. Contributors now find what their pull request shows and what to do in one place, with links to the design doc for the reasons, and the design doc points them there. Generated-by: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01NyQq9U7i5HhjDgrQ9qd3gq
A pull request closed because project CI ran for it although it should not have stays closed when its author reopens it; only a maintainer can reopen it, unlike one closed for changing the gate. Generated-by: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01NyQq9U7i5HhjDgrQ9qd3gq
The pull request guide, the breeze CI commands page and the triage guide each restated part of how fork CI works, and the breeze page had gone stale (a one-week closure, drafting until green). Each now keeps what its reader acts on and links to the contributor section or the design. Generated-by: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01NyQq9U7i5HhjDgrQ9qd3gq
Adding the label by hand starts no project CI, and until the next monitor run a green fork result still lets the pull request merge. A rebase moves the head past that result, and a close and reopen starts project CI. Generated-by: Claude Opus 5 Claude-Session: https://claude.ai/code/session_01NyQq9U7i5HhjDgrQ9qd3gq
potiuk
force-pushed
the
fork-ci-docs-consolidate
branch
from
November 15, 2026 23:18
23d2c2a to
1d4669f
Compare
potiuk
enabled auto-merge (squash)
November 15, 2026 23:22
Contributor
Backport failed to create: v3-4-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker c4aa191 v3-4-testThis should apply the commit to the v3-4-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On the dev list, the fork CI (ADIP-12, formerly AIP-120) design doc and the contributor docs were said to overlap, with the contributor docs mixing what to do with why the monitor does it. This keeps in the contributor docs what contributors need, and links to the design doc for the reasons.
contributing-docs/18_contribution_workflow.rst, "CI in your fork": the setup steps are unchanged.ready for maintainer reviewuntil the new run is green;use project cimeans for them;fork ci required;apacheorg membership makes a committer count as external.ci-in-your-forkanchor, used by the bot's comments and other docs, is unchanged.contributing-docs/25_maintainer_pr_triage.md: drops a paragraph that repeated theneeds project cirule above it.use project ci;CI passedto turnpendingbefore merging.CI passedcheck" section. That also drops the "15 minutes" that disagreed with the 5-minute monitor.contributing-docs/05_pull_requests.rst:dev/breeze/doc/08_ci_tasks.rst: thefork-ci-reconcileandapprove-workflow-runssections now say what each command is for and link to the design docs.dev/breeze/doc/ci/08_fork_ci_for_external_contributors.md:use project ciwindow now says to rebase or close and reopen after adding the label by hand. A rebase closes the window, because the fork result stays on the old commit.Two other open PRs change what these docs describe, and whichever merges second updates the text:
Tested: static checks pass on the changed files, including link checks, markdownlint and the RST checks.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Claude Opus 5) following the guidelines
🤖 Generated with Claude Code
https://claude.ai/code/session_01NyQq9U7i5HhjDgrQ9qd3gq