Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Investigate how we are dealing with renaming of files 🗃️ #83

Open
jamacku opened this issue Aug 8, 2022 · 2 comments
Open

Investigate how we are dealing with renaming of files 🗃️ #83

jamacku opened this issue Aug 8, 2022 · 2 comments
Assignees
Labels

Comments

@jamacku
Copy link
Member

jamacku commented Aug 8, 2022

Type of issue

Bug Report

Description

There might be issue with differential-shellcheck when shell script is renamed (and contain some changes)

Describe the solution you'd like

No response

@mpoberezhniy
Copy link
Contributor

I renamed one of directories in my repository and differential shellcheck displayed all the defects from that directory in the log, but GitHub did not show any of those.

This is a bit unexpected because no warnings were shown but the action was red.

@jamacku
Copy link
Member Author

jamacku commented May 17, 2024

GitHub is doing some pre/post-processing of SARIF files (but there is no documentation). It includes its own fingerprints if no fingerprints are available. This is why differential-shellcheck sometimes reports some defects, but the GitHub SARIF upload is green.

The latest version should improve this situation, as it has the latest version of csdiff, which now also generates fingerprints.

Renaming directories/files might still be an issue. But there are differential actions for Python that is able deal with renames and moves.

This is definitely something that I would like to get fixed. It is long overdue.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
Development

No branches or pull requests

2 participants