search

ipdxco / github-as-code

GitHub Configuration as Code
19 stars 7 forks source link

Remove clutter resulting from archived repos #115

Open BigLep opened 9 months ago

BigLep commented 9 months ago

The problem

These .yaml files can be unwieldy and the problem is exasperated by intermixing of archived repos with unarchived repos.

Ideas

I think it would be help to have a view on all the repos that aren't archived. Some ideas:

  1. Put all the archived repos at the bottom of the file. (I still don't like this one as much because archived repos will show up when doing text search for "team X" when trying to answer "what teams does X have permissions to").
  2. If a repo is archived, don't display any other properties about the repo in github-mgmt. (The downside of this approach is that you could miss if there are admins of the repo who can then self-service unarchive. There will be some cases where that is a security concern, and it would be ideal to have more visibility into this possibility.)
  3. Have an optional separate .yaml that contains archived repos that gets merged in at "build" time. This would allow a dedicated separate file (e.g., archived_repos.yaml).
    • Generalizing this, maybe github-mgmt can be configured to do a merge of any specified files, which lets repo organizers decide if/how they want to break up their yaml file in general?
  4. Go the IPFS route and actually have an "inactive" org "ipfs-inactive". Archived projects can get moved there. This makes things very clear about the maintenance status and also solves the declutter problem.