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

Allow a target of "not worse" #97

Open
dennis-sig opened this issue Apr 26, 2022 · 2 comments
Open

Allow a target of "not worse" #97

dennis-sig opened this issue Apr 26, 2022 · 2 comments

Comments

@dennis-sig
Copy link
Contributor

Requested/proposed by a client to @SebGondron. This type of suggestion fits well with our boy scout rule storyline, and it's a very pragmatic solution for systems that are very large and/or old and/or use older technologies.

@JohanVT
Copy link

JohanVT commented Nov 3, 2022

We are currently switching from FTP upload to SigridCI for several scientific/computational/modeling applications, using a mix of technologies (Fortran, C#, Python, Ruby, and more) within the same project.

I decided to set the targetquality to 0 because the results of other values feel too random.
The "not worse" target would be very helpful!

Assuming "not worse" is determined for existing code by comparing the results of the same sources. For new source files it's probably best to keep using the targetquality?

@MichielCuijpers
Copy link
Member

thanks @JohanVT

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

No branches or pull requests

3 participants