- Notifications
You must be signed in to change notification settings - Fork 378
Open
Description
First of all: Great service!
Last week I received I "CodeTriage misses you" email (yeah, I know... 😞) that suggested me to engage with an archived repo.

I don't think that any archived repository should be suggested to a user (both on email suggestions and through the web application)
Expected Behavior
Archived repos probably should be removed from the platform.
They shouldn't be suggested on daily emails or through the web interface "Open source projects on GitHub that need your help." functionatlity
Current Behavior
Archived repos are handled the same way as any other repo.
Possible Solution
Periodically check if the repo was archived then:
- Record it:
- Save to a flag column in the database
- Add a default_scope to the model
OR
- Delete it
(Probably could expand the the existing Checks if repos have been deleted on GitHub task if necessary to unnecessary requests to GH's api)
Steps to Reproduce (for bugs)
Metadata
Metadata
Assignees
Labels
No labels