ISOC-3693 Secret scanning alerts backfill #2335
Merged
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.
What's in this PR?
Adding support to backfill the secret scanning alerts along with the other entities. The backfill behaviour is in sync with the backfill for existing entities.
https://hello.atlassian.net/wiki/spaces/CDX/pages/2748121866/LDR+How+do+we+backfill+vulnerabilities+for+existing+GitHub+for+Jira+customers
Why
Part of the work to integrate GitHub with Security in Jira
https://hello.atlassian.net/wiki/spaces/CDX/pages/2673460294/RFC+GitHub+for+Jira+Security
Added feature flags
ENABLE_GITHUB_SECURITY_IN_JIRA
Affected issues
ISOC-3693
How has this been tested?
Unit Test