ci: add interrogate to github actions

[terriko]

• chore: add interrogate to linters called by pre-commit #3491 added interrogate to our pre-commit config, which means people locally will run it, but it's not yet running in github actions

The line to change is here:

https://github.com/intel/cve-bin-tool/blob/main/.github/workflows/linting.yml#L20

It's possible that you'll need to tweak the % allowed or the files checked before it'll pass in CI as well. I won't be able to merge it unless it's passing, so consider that part of this issue!

[sratslla]

I am working on this

[mhdsalih2000]

hi, Iam newbie in opensource contribution. I don't understand the terms in the issue section. how do I overcome that . can anyone pls explain how I can understand the issue

[terriko]

@mhdsalih2000 Don't be afraid to search for terms you don't understand! DuckDuckGo is surprisingly helpful at times if you're not sure what stuff like "pre-commit" or "github actions" means. You're probably going to have to do a lot of that on your own, and I suggest you work on learning to ask more specific questions. For example, "I don't understand any of this" is less likely to get an answer than something like "why can't you merge this unless it's passing?"

That said, here's a few links for this particular issue. It's asking someone to adding another tool for checking code quality to our standard set that's being run on all code before it gets integrated as part of cve-bin-tool. You can read about the code quality tools we're already using here to get an idea of what they're for and how we use pre-commit to help people run them:
https://github.com/intel/cve-bin-tool/blob/main/CONTRIBUTING.md#running-linters

This one, called "interrogate" can be read about here: https://github.com/econchick/interrogate