-
Notifications
You must be signed in to change notification settings - Fork 148
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
[Feature Request] Skip archived repositories from being configured #443
Comments
Seems that there is already a WIP PR that tackles this issue: #193 |
We are seeing this, although it is coming through as 403. |
#193 is different than just ignoring archived repos. Example error log from trying to apply changes to archived repos. I agree that ignoring archived repos will positively effect the rate limit, while also removing noise from the logs. We needed to filter out "Repository was archived so is read-only" from our alerting.
|
Yeah, we are getting a bunch of 403s from trying to incorrectly update archived repos. A fix for this would help a lot with rate-limiting and the volume of logs |
Up-vote for configuration options to exclude archived repos from being matching by settings.yml or a suborg definition (Rate-Limits, Logging, Performance). |
New Feature
When configuring (e.g., topics, vulnerability, general settings, etc. ) archived repositories, safe-settings receives HTTP 422 errors. Since the intention of archived repositories is to not use them anymore there is no reason to configure them.
Therefore my proposal is to exclude those in safe-settings. This will have a positive impact on the rate limit.
The text was updated successfully, but these errors were encountered: