Simplify fork remote detection in AGENTS.md#62748
Merged
kaxil merged 1 commit intoapache:mainfrom Mar 3, 2026
Merged
Conversation
Use `origin` directly when it isn't `apache/airflow` instead of requiring a GitHub username lookup and remote scan. Most contributors already have their fork as `origin` (e.g. `astronomer/airflow`), so the extra steps were unnecessary overhead.
kaxil
requested review from
amoghrajesh,
ashb,
jason810496,
jscheffl,
potiuk and
shahar1
as code owners
potiuk
approved these changes
Mar 3, 2026
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
2 participants
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.
The previous instructions required agents to look up the GitHub username via
gh api user, scan all remotes for a matching fork, and create one named afterthe user. This is unnecessary when
originalready points to the user's fork,which is the common case (e.g.
origin → astronomer/airflow).Now the logic is: if
originisn'tapache/airflow, use it directly. Only fallback to searching other remotes or creating a fork when
originis the upstreamrepo.
Was generative AI tooling used to co-author this PR?