-
Notifications
You must be signed in to change notification settings - Fork 1
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
Lukas/gh/fix ort reuse scanner #249
Conversation
Reviewer's Guide by SourceryThis pull request introduces a new escript, Sequence diagram for ORT scanner initializationsequenceDiagram
participant OS as Operating System
participant ort-scanner.es
participant git
participant sha1sum
OS->>ort-scanner.es: Execute init command with analyzer result and git repo path
ort-scanner.es->>git: git rev-parse HEAD (get Git SHA)
git-->>ort-scanner.es: Returns Git SHA
ort-scanner.es->>sha1sum: sha1sum (calculate SHA1 sums of files)
sha1sum-->>ort-scanner.es: Returns SHA1 sums
ort-scanner.es->>OS: Write scan result to file
Sequence diagram for ORT scanner restore cachesequenceDiagram
participant OS as Operating System
participant ort-scanner.es
OS->>ort-scanner.es: Execute restore-cache command with input and cache scan results
ort-scanner.es->>ort-scanner.es: Check files to restore from cache
ort-scanner.es->>ort-scanner.es: Restore scan results from cache
ort-scanner.es->>OS: Write updated scan result to file
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
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.
Hey @garazdawi - I've reviewed your changes - here's some feedback:
Overall Comments:
- Consider adding a flag to disable the reuse scan step, as it might not always be desired.
- The new script introduces a lot of complexity; ensure it's thoroughly tested and handles edge cases gracefully.
Here's what I looked at during the review
- 🟢 General issues: all looks good
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
48fbe58
to
696803e
Compare
696803e
to
93d7162
Compare
When scanning code for licenses, we now also include data from `reuse lint` into the results. This allows us to have more consistent results as reuse scanning is predictable in a way that scancode is not. We still keep scancode as it can find licenses in files that do not yet use the `reuse` standard.
93d7162
to
e3b8f09
Compare
No description provided.