[Github parser] Parse dependabot alert number and add link in description #8050
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
Maffooch
approved these changes
May 3, 2023
devGregA
approved these changes
May 4, 2023
blakeaowens
approved these changes
May 4, 2023
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.
It's currently quite unusable to view dependabot alerts because they don't give a direct link into the Github platform, to maybe triage things there, get more details... view the PR attached etc...
Funny thing is, Github doesn't return a direct link to the alert, so you must either return the repo URL, or at least the full name with the org/owner, and build from there.
Another thing that I can't fix unfortunately: directly linking to the file in Github is hard, because yet again, Github's API isn't telling you the branch where the issue was detected. Dependabot opens PRs properly though, so maybe you could introspect the PR it has opened and find out the target branch... if someone reads this and wants to bother