Skip to content

Define a default-off Admins team policy #95

Description

@devantler

🤖 Generated by the Codex Daily AI Engineer instance.

Objective

Define a separate admins team and its repository-admin grants as a default-off declarative policy slice under parent #53.

Details

The maintainer chose a separate Admins team so admin privileges remain isolated from the canonical maintainers team. This slice declares the new team, adds devantler as its maintainer, and grants admin on the 19 active portfolio repositories:

  • .github
  • actions
  • agent-plugins
  • agent-skills
  • ascoachingogvaner
  • aws
  • dotnet-template
  • fleet-gitops
  • gitops-tenant-template
  • go-template
  • homebrew-tap
  • ksail
  • maintenance
  • monorepo
  • platform
  • platform-template
  • provider-upjet-unifi
  • unifi
  • wedding-app

The policy must remain absent from the deployed root Kustomization until a separate activation slice is reviewed. The archived reusable-workflows repository is intentionally excluded.

Checklist

  • Declare a creatable Team/admins with no Delete management policy.
  • Declare the maintainer membership and 19 TeamRepository resources with admin permission.
  • Add a feature Kustomization that renders the complete enabled policy.
  • Prove the normal deploy/ render is disabled and the feature render is valid.
  • Document the activation boundary and exact repository scope.

Dependencies

Parent #53 records the coverage goal and the now-resolved GitHub App Members-permission prerequisite. Activation remains a follow-up under #53.

Notes

This is the first child increment of #53. It deliberately defines policy without changing live organization permissions.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions