Increase DAYS_UNTIL_STALE from 30 to 180 #140
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Per Jay at Mars, the broker will not import a Repo that has not been updated in the last 30 days regardless of its representation status in Fossa. This changes the number of days until a commit is considered stale to 180.
Acceptance criteria
Users should now be able to import commits up to 180 days old into the broker.
Testing plan
n/a
Risks
Are there any other areas where a commit older than 30 days could cause an issue?
References
https://fossa.zendesk.com/agent/tickets/7174
Checklist