Remove 30 day staleness limit restriction for integration scanning #141
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
Broker has a 30 day staleness limit on git commits. This has caused frustrations for Mars as they have many repos that they want to import to Broker which are not frequently updated (last commit > 30 days). As a result, we want to remove this staleness limit.
Acceptance criteria
Remove staleness limit and ensure that repo can scan repos with git commits > 30 days
Changes will need to made to this function
The staleness limit is defined by this const variable
Testing plan
Manually test changes against repos with branches / tags with their last change being > 30 days.
Repos Tested Against:
Risks
References
Add links to any referenced GitHub issues, Zendesk tickets, Jira tickets, Slack threads, etc.
Example:
Checklist