One repository-owned .ci.yaml only, using the already-qualified shared pipeline and explicit default-branch scoped delegation. Original tracked-files command and configured branch scope retained; shared quality/security/result handling runs once after merge. The initial PR is checked by the existing legacy policy because only default-branch configuration can opt in. No app, release/native/local workflow, credential or publisher change. Permanent legacy retirement follows only an actual successful canonical merge run; no extra proof commit.
One repository-owned .ci.yaml only, using the already-qualified shared pipeline and explicit default-branch scoped delegation. Original tracked-files command and configured branch scope retained; shared quality/security/result handling runs once after merge. The initial PR is checked by the existing legacy policy because only default-branch configuration can opt in. No app, release/native/local workflow, credential or publisher change. Permanent legacy retirement follows only an actual successful canonical merge run; no extra proof commit.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
One repository-owned .ci.yaml only, using the already-qualified shared pipeline and explicit default-branch scoped delegation. Original tracked-files command and configured branch scope retained; shared quality/security/result handling runs once after merge. The initial PR is checked by the existing legacy policy because only default-branch configuration can opt in. No app, release/native/local workflow, credential or publisher change. Permanent legacy retirement follows only an actual successful canonical merge run; no extra proof commit.