-
Notifications
You must be signed in to change notification settings - Fork 31
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
Toil reduction: basic listing of a repo should not require an entry in repos.yml. #4259
Comments
sengi
added a commit
that referenced
this issue
Jan 9, 2024
This is really just hacking around a bug (#4259), but for now it seems that when a private repo is listed without `private_repo: true`, CI fails in at least some circumstances.
sengi
added a commit
that referenced
this issue
Jan 30, 2024
We still need to set these for now, until we fix #4259.
D'oh. Thanks @ChrisBAshton 😄 TIL |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
repos.yml
duplicates a bunch of information that's either already available from the GitHub API or we can easily add using tags. This is a source of toil and frustration.An entry in
repos.yml
should only be necessary for specifying metadata that we can't easily get from GitHub tags.For example, we already tag our repos with
govuk
.type
is a natural fit for a tag.description
should come from the repo description and not be duplicated here.retired
should be inferred if the repo is archived. Team ownership could probably be a tag.The text was updated successfully, but these errors were encountered: