(airflow-steward) branch main updated: build(asf): add collaborator, disable Copilot review, scaffold atr-release env (#53)

[po...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow-steward.git


The following commit(s) were added to refs/heads/main by this push:
     new 6a041f4  build(asf): add collaborator, disable Copilot review, scaffold atr-release env (#53)
6a041f4 is described below

commit 6a041f49848228b03c223a8d754521bbe677337a
Author: Jarek Potiuk <ja...@potiuk.com>
AuthorDate: Tue May 5 10:40:57 2026 +0200

    build(asf): add collaborator, disable Copilot review, scaffold atr-release env (#53)
    
    Three asf.yaml additions per maintainer ask:
    
    - `collaborators: [andreahlert]` — gives external triage rights without
      apache-org membership. ASF Infra caps the list at 10; one entry now,
      room to grow.
    
    - `copilot_code_review: { enabled: false }` — explicitly disables the
      GitHub Copilot per-PR auto-review ruleset on the default branch. The
      framework's review loop is human-driven (`pr-management-code-review`
      skill + maintainer review); Copilot's automatic review comments
      duplicate / contradict that loop. The explicit `enabled: false` is
      the asf.yaml directive's required form to actively remove the
      ruleset if it was previously configured.
    
    - `environments.atr-release` — deployment environment scaffolded for an
      eventual release workflow that publishes through ASF Trusted Releases
      (ATR). `protected_branches: true` restricts deploy-from to protected
      branches (today: `main`); `prevent_self_review: true` for the
      required-reviewer flow once one is added; `wait_timer: 0` for now.
      Required reviewers / PMC sign-off can be wired in when the release
      workflow lands.
    
    Project board (`features.projects: true`) and discussion
    (`features.discussions: true` + `notifications.discussions:
    commits@airflow.apache.org`) are already set on main; left unchanged.
    
    Generated-by: Claude Code (Claude Opus 4.7)
---
 .asf.yaml | 30 ++++++++++++++++++++++++++++++
 1 file changed, 30 insertions(+)

diff --git a/.asf.yaml b/.asf.yaml
index 7eb3528..d855b00 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -47,6 +47,36 @@ github:
     allow_update_branch: true
     del_branch_on_merge: true
 
+  # External triage collaborators — GitHub IDs that get triage rights
+  # without being added to the apache org. ASF Infra caps this list
+  # at 10 entries; exceptions need a vp-infra@apache.org request.
+  collaborators:
+    - andreahlert
+
+  # Disable the GitHub Copilot automatic-code-review ruleset on the
+  # default branch. The framework's review workflow is human-driven
+  # (`pr-management-code-review` skill + maintainer review), and
+  # Copilot's per-PR comments duplicate / contradict that loop.
+  # The explicit `enabled: false` is required to actively remove the
+  # ruleset if it was ever previously configured (per the asf.yaml
+  # `copilot_code_review` directive).
+  copilot_code_review:
+    enabled: false
+
+  # Deployment environments — created here so an eventual release
+  # workflow can target them without touching the GitHub UI. The
+  # `atr-release` environment scaffolds release publishing through
+  # ASF Trusted Releases (ATR); the protected-branches policy
+  # ensures only `main` (and any future protected release branches)
+  # can deploy. Required reviewers can be added later if the
+  # release flow needs PMC sign-off at deploy time.
+  environments:
+    atr-release:
+      wait_timer: 0
+      prevent_self_review: true
+      deployment_branch_policy:
+        protected_branches: true
+
   # No `protected_branches:` block by design — branch protections are
   # configured directly in GitHub for now. Add here when the project's
   # release / branching policy stabilises.