[GH-ISSUE #55] The joys of codeql packs and suites #11

New issue

Open

opened 2026-03-02 04:07:48 +03:00 by kerem · 0 comments

kerem commented

2026-03-02 04:07:48 +03:00

Owner

Originally created by @danielcuthbert on GitHub (Dec 26, 2025).
Original GitHub issue: https://github.com/gadievron/raptor/issues/55

When I was building out the the codeql aspect of RAPTOR, I stupidly used hardcoded paths for my codeql suites and packs via env variables. Tsk tsk, i know, I've beaten myself a lot, don't you worry.

The lovely chap that is @AndrewMohawk did see this and issued a PR https://github.com/gadievron/raptor/pull/38 but we need to do a bit more here.

When codeql runs, it needs something to eat and use and this is where the env came into play, but in reality we should be using the codeql cli to pull them down before the workflow is initiated and then go forth and make gorgeous music.

I've asked Andrew to amend the placement of the function and to add some error handling but this is a good issue and shows the power of this community

Originally created by @danielcuthbert on GitHub (Dec 26, 2025). Original GitHub issue: https://github.com/gadievron/raptor/issues/55 When I was building out the the codeql aspect of RAPTOR, I stupidly used hardcoded paths for my codeql suites and packs via env variables. Tsk tsk, i know, I've beaten myself a lot, don't you worry. The lovely chap that is @AndrewMohawk did see this and issued a PR https://github.com/gadievron/raptor/pull/38 but we need to do a bit more here. When codeql runs, it needs something to eat and use and this is where the env came into play, but in reality we should be using the codeql cli to pull them down before the workflow is initiated and then go forth and make gorgeous music. I've asked Andrew to amend the placement of the function and to add some error handling but this is a good issue and shows the power of this community