Skip to content

Establish mechanism to centrally propagate repo settings #26

Open
@leecalcote

Description

@leecalcote

Current Behavior

Managing a large number of repos within an org and also across orgs is burdensome (and part of the attraction to GH Enterprise).

Desired Behavior

Some of the tooling needed to help with org/repo management is simple enough to either create or to use from existing tooling. Examples of existing tools:

Implementation

Acceptance Tests

  1. Initially, propagation of a central list of GitHub issues is the goal.
  2. If we are able to propagate other settings as well, then that's a bonus, so long is the framework isn't burdensome.

Mockups


Contributor Guide

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/ciContinuous integration | Build and releasearea/devopshelp wantedExtra attention is neededissue/willfixThis issue will be worked onkind/choreNecessary task

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions