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

Organization-level CodeQL Query packs #16555

Open
martinvks opened this issue May 22, 2024 · 2 comments
Open

Organization-level CodeQL Query packs #16555

martinvks opened this issue May 22, 2024 · 2 comments
Labels
question Further information is requested

Comments

@martinvks
Copy link

Hi,

do you have any plans to add support for custom query suites in default setup?
That is, something similar to the organization-level CodeQL model packs described in this blog post.

@martinvks martinvks added the question Further information is requested label May 22, 2024
@jf205
Copy link
Contributor

jf205 commented May 22, 2024

Hi @martinvks

We are working on making code scanning default setup more customizable using CodeQL packs. Custom CodeQL query packs will likely be coming up next but we don't have an exact timeframe yet.

Your feedback can help us make sure we integrate packs into code scanning in the right way. Can you say a little more about how you use custom CodeQL queries and how you would like to be able to use them in code scanning please?

@martinvks
Copy link
Author

Hi @jf205, thank you for the quick reply.

We are using GHES and have a reusable workflow for code scanning to avoid duplication. In this workflow we specify queries to be run, in addition to the default queries. We also exclude some of the default queries with a custom configuration file. I find that scaling and maintaining our current setup is challenging as it requires adding a caller workflow in each repository we want to onboard. However, if we go with default setup we can only choose between the built in query suites. I understand that the configuration options in default setup is more limited than with advanced setup but being able to specify additional query packs would go a long way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants