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.

Sign up for GitHub

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

Jump to bottom

Prune excess entries in RepoIndex #1398

Open
another-rex opened this issue Jun 19, 2023 · 1 comment
Open

Prune excess entries in RepoIndex #1398

another-rex opened this issue Jun 19, 2023 · 1 comment
Labels
backlog Important but currently unprioritized cleanup Code hygiene and cleanup needs-gcp-infra-access To be able to adequately work on this issue will require access to GCP infrastructure techdebt Technical debt to be paid down

Comments

@another-rex
Copy link
Contributor

The configs has been updated a few times, and some of the entries in RepoIndex is now not in the configs. Create a script to prune them.
@github-actions GitHub Actions
Copy link

This issue has not had any activity for 60 days and will be automatically closed in two weeks

@github-actions github-actions bot added the stale The issue or PR is stale and pending automated closure label Jul 23, 2024
@andrewpollock andrewpollock added backlog Important but currently unprioritized cleanup Code hygiene and cleanup needs-gcp-infra-access To be able to adequately work on this issue will require access to GCP infrastructure techdebt Technical debt to be paid down labels Jul 26, 2024
@oliverchang oliverchang removed the stale The issue or PR is stale and pending automated closure label Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backlog Important but currently unprioritized cleanup Code hygiene and cleanup needs-gcp-infra-access To be able to adequately work on this issue will require access to GCP infrastructure techdebt Technical debt to be paid down
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@oliverchang @andrewpollock @another-rex