-
Notifications
You must be signed in to change notification settings - Fork 574
🐛 Ensure % character in the artifactLocation in sarif output are escaped #4619
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
Conversation
e9eda85
to
d1a8b1a
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4619 +/- ##
==========================================
+ Coverage 66.80% 68.37% +1.56%
==========================================
Files 230 249 +19
Lines 16602 18814 +2212
==========================================
+ Hits 11091 12864 +1773
- Misses 4808 5097 +289
- Partials 703 853 +150 🚀 New features to boost your workflow:
|
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.
Thank you! Could you please correct your last commit for DCO?
https://github.com/ossf/scorecard/pull/4619/checks?check_run_id=41958169840
Signed-off-by: Uwe L. Korn <[email protected]>
Signed-off-by: Uwe L. Korn <[email protected]>
Signed-off-by: Uwe L. Korn <[email protected]>
Done! Sorry, I'm not used to that. |
No worries, thanks for sending the patch. It's common for contributors to need to fix DCO. Keep an eye out for the next scorecard-action release. We are probably due for one soon. |
What kind of change does this PR introduce?
(Is it a bug fix, feature, docs update, something else?)
What is the current behavior?
Currently if a filename contains a
%
character it is passed through in plain text in the result insarif
file. If the location is later parsed again, an URL-decoder will stumble upon it as it tries decode the escape sequence.As an example see the following
scorecard-action
where the SARIF upload failed: https://github.com/Quantco/copier-template-python-open-source/actions/runs/14924466359What is the new behavior (if this is a feature change)?**
%
characters are escaped in the SARIF output.Which issue(s) this PR fixes
NONE
Special notes for your reviewer
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)