@romani - yeah, that's basically what we're doing, with just a bit more of a manual process. We are checking in the violations and then any updates to that file result in a change in SCM, and we call it out on PRs and things like that.
Setting up a file to be a suppression would be a great idea, but I wonder if it's feasible since changing code around something would cause the lines where the violations that occur to be changed.
interesting. So you could have a build that produces the "suppression" file that could then be fed back into future builds.
I think this would work well. The only thing that I would say that would beneficial with this is to have some way of notifying if there was an unnecessary suppression. It would help to identify situations where an issue has been fixed but the suppression file wasn't updated.
I am new to open source community , i would love to start my journey from this community .
I am also willing to take part in GSoC 2019 as well .
I know JAVA ,C ,C++ , MySQL and right now learning python as well .
How can i contribute to this community ?? Please Guide me!!!!!