Skip to content
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

chore: don't trim trailing whitespace on fixture snapshots #608

Merged
merged 1 commit into from
Oct 25, 2023
Merged

chore: don't trim trailing whitespace on fixture snapshots #608

merged 1 commit into from
Oct 25, 2023

Conversation

G-Rath
Copy link
Collaborator

@G-Rath G-Rath commented Oct 25, 2023

This makes it easier to work with for IDEs

@codecov-commenter
Copy link

Codecov Report

Merging #608 (98f2617) into main (c00f630) will not change coverage.
Report is 2 commits behind head on main.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #608   +/-   ##
=======================================
  Coverage   80.61%   80.61%           
=======================================
  Files          78       78           
  Lines        5334     5334           
=======================================
  Hits         4300     4300           
  Misses        866      866           
  Partials      168      168           

@another-rex another-rex merged commit dfef890 into google:main Oct 25, 2023
8 checks passed
@G-Rath G-Rath deleted the dont-trim-newlines branch October 25, 2023 00:33
another-rex added a commit to another-rex/osv-scanner that referenced this pull request Oct 26, 2023
* Add name field to sarif rule output (google#600)

Fixes google#599

* fix: trim leading and trailing newlines off SARIF output (google#606)

I don't know a lot about SARIF so maybe these are required but that
would be surprising to me whereas trimming these off make it a bit
consistent for editors and such.

Obviously if these are required then lets close this PR

* Update release pipeline (google#602)

Update the release pipeline to have it be manually triggered, and create
a tag itself if checks and scans are successful.

It looks something like this:

![image](https://github.com/google/osv-scanner/assets/106129829/8258a7d3-3438-46f7-82cd-49c2b4056ecf)

The release doc has been updated to follow this new workflow.

* chore: don't trim trailing whitespace on fixture snapshots (google#608)

This makes it easier to work with for IDEs

* Prepare for 1.4.2 release (google#609)

* Update jekyll feed, for some reason renovatebot can't figure out how to update this

* Fix documentation for github action

* Set upload tag name

---------

Co-authored-by: Gareth Jones <Jones258@Gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants