Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove clutter resulting from archived repos #115

Open
BigLep opened this issue Feb 8, 2024 · 0 comments
Open

Remove clutter resulting from archived repos #115

BigLep opened this issue Feb 8, 2024 · 0 comments

Comments

@BigLep
Copy link
Contributor

BigLep commented Feb 8, 2024

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?
  1. 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant