-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for more GIT SCMs in finding view for the finding URL #9710
Conversation
Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.
Note 🔴 Risk threshold exceeded. Adding a reviewer if one is configured in notification list: @mtesauro @grendel513 Tip Get answers to your security questions. Add a comment in this PR starting with @DryRunSecurity. For example...
Powered by DryRun Security |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now THAT is a function name...
test_get_file_path_with_link_and_source_code_management_uri_gitea_or_codeberg_project_with_commithash_and_line
…fectDojo#9710) * Add support for more GIT SCMs * fix flake8 issue * docs: added other supported SCM to the documentation --------- Co-authored-by: Eugeniu David <eugeniu.david@mic-cust.com>
Description
Reworked the finding URL generation method to cover more GIT SCMs (github, gitlab, gitea, codeberg, bitbucket) by default. Also unified the bitbucket and github link generation methods into 1.
Test results
Added two new tests to test the new functionality, make sure that the function generates the correct URL for gitea.