Include short example of limiting build directories

[hohn]

Why:

Add example of limiting compiled language builds

What's being changed:

Add example of limiting compiled language builds

Check off the following:

• I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
• For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

• This pull request impacts the contribution experience
  • I have added the 'writer impact' label
  • I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

Automatically generated comment ℹ️

This comment is automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the staging site. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Staging	Production	What Changed
content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-the-codeql-workflow-for-compiled-languages.md	Modified	Original

[ramyaparimi]

@hohn
Thanks so much for opening a PR! I'll get this triaged for review ⚡

[felicitymay]

@hohn - thank you for this example ✨

Since this article is already very long and the example is for compiled languages only, I think it might be better to add the example to the linked article on configuring the CodeQL workflow for compiled languages.

I don't think that I can move the example on your fork, but if you can move the example then I can edit it to bring it into line with our guidelines.

The Repo freeze check failure will be fixed when we update this branch from main, so can be ignored.

[hohn]

Hi @felicitymay, I moved the example to a separate section in the file you linked.

[felicitymay]

I moved the example to a separate section in the file you linked.

@hohn - thank you so much 💖
I've edited the text to bring it more into line with our style guide.

Somehow, yesterday I managed to overlook the fact that your example calls the CodeQL CLI directly, when this article is aimed at CodeQL action users 🤦🏻‍♀️

I've added a suggestion with what I think the relevant content would be for the CodeQL action. Could you take a look?

I think the CodeQL CLI example itself could be added after the Multiple language example in this article about using the CLI directly.

[felicitymay]

I think the test failure is spurious.

[felicitymay]

@hohn - is there an alternative approach that would work for header-only C++ libraries? If not, can/should we say why this doesn't work for them?

[felicitymay]

We discussed this change with the PR author. We agreed that, although this example is helpful in some cases, it's not generally enough for inclusion in the docs. Omitting specific directories from compiled language extraction is an area that the development team is working on. They plan to document this when work is complete.

[felicitymay]

@hohn - many thanks for suggesting this example and bringing this discussion to the fore. It's much appreciated.