Skip to content

Conversation

@GrosQuildu
Copy link
Collaborator

@GrosQuildu GrosQuildu commented Feb 27, 2025

Add more information about installing and unit-testing custom codeql rules.
One link is now broken, but will the upstream file will be crated soon.

@github-actions
Copy link

github-actions bot commented Feb 27, 2025

PR Preview Action v1.6.3
Preview removed because the pull request was closed.
2025-12-23 13:28 UTC

@GrosQuildu GrosQuildu requested a review from elopez February 27, 2025 14:46
Copy link

@fegge fegge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great! I added a few language recommendation. Nothing big.

@GrosQuildu GrosQuildu requested a review from Vasco-jofra June 9, 2025 09:52
@GrosQuildu GrosQuildu requested a review from fegge June 17, 2025 11:04
@GrosQuildu
Copy link
Collaborator Author

Can we get this merged?

@GrosQuildu
Copy link
Collaborator Author

ping

@elopez elopez merged commit 3e636e7 into main Dec 23, 2025
4 of 5 checks passed
@elopez elopez deleted the codeql-install-updates branch December 23, 2025 13:27
of the version you want, you can use `"*"` which always resolves to the latest
version.)

### Installing the new packs
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this step still necessary if you've properly set up your workspace with codeql-workspace.yml?

I ask because I've had some trouble between using codeql-workspace.yml vs. .codeqlmanifest.json vs. --search-path vs. --additional-packs. And generally just using codeql-workspace.yml has fixed my problems 🤷

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure? You need codeql to known the location somehow, would it auto-pick locally cloned repo?
Also the pack download is easier than cloning the repo.

Fell free to update this section anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants