Skip to content

Add CODEOWNERS for agentic instruction files#62618

Merged
potiuk merged 1 commit intoapache:mainfrom
potiuk:add-codeowners-for-agentic-instructions
Feb 28, 2026
Merged

Add CODEOWNERS for agentic instruction files#62618
potiuk merged 1 commit intoapache:mainfrom
potiuk:add-codeowners-for-agentic-instructions

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Feb 28, 2026

Add CODEOWNERS entries for all agentic instruction files in the repository so that
PRs modifying AI agent instructions get reviewed by the people who maintain them.

Covered paths (all owned by @potiuk @kaxil @jscheffl @amoghrajesh @ashb @sjyangkevin):

  • /AGENTS.md
  • /.github/instructions/
  • /airflow-core/src/airflow/api_fastapi/execution_api/AGENTS.md
  • /providers/AGENTS.md
  • /.github/skills/

Was generative AI tooling used to co-author this PR?
  • Yes — Claude Opus 4.6

Generated-by: Claude Opus 4.6 following the guidelines

@boring-cyborg boring-cyborg bot added area:dev-tools backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch labels Feb 28, 2026
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@potiuk potiuk force-pushed the add-codeowners-for-agentic-instructions branch from 85be137 to 0c975ac Compare February 28, 2026 10:41
@potiuk potiuk requested a review from bugraoz93 February 28, 2026 10:42
@potiuk
Copy link
Member Author

potiuk commented Feb 28, 2026

Anyone else wants to be added :)?

@potiuk potiuk merged commit 25c0eb5 into apache:main Feb 28, 2026
62 checks passed
@potiuk potiuk deleted the add-codeowners-for-agentic-instructions branch February 28, 2026 10:55
@github-actions
Copy link

Backport failed to create: v3-1-test. View the failure log Run details

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-1-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 25c0eb5 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

Dev-iL added a commit to Dev-iL/airflow that referenced this pull request Mar 1, 2026
jason810496 pushed a commit that referenced this pull request Mar 1, 2026
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-1-test Mark PR with this label to backport to v3-1-test branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants