Add CodeQL workflow for GitHub code scanning #588
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![lgtm-com[bot]](https://avatars.githubusercontent.com/in/17324?s=60&v=4){kind=small}
* feat(website): rename root to foxxie.xyz * fix: tsconfig ver
* feat: add statuspage * fix: deps * fix:tests * fix: tests * fix: :p * fix: :p * Update codecov.yml * Update codecov.yml * build: pkgs with nx * fix: scripts * fix: scripts
Build ran for b5fb479 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* docs: update README.md [skip ci] * docs: update .all-contributorsrc [skip ci] * Update README.md * Update .all-contributorsrc Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com> Co-authored-by: Ruff <73779441+Ruffpuff1@users.noreply.github.com>
* ci: update configs * Update bump-package.yml
* fix(kettu): type errors * f
Co-authored-by: Renovate Bot <bot@renovateapp.com>
Build ran for 30e567e
Co-authored-by: Renovate Bot <bot@renovateapp.com>
* feat(foxxie): use sanitize * fix: comment out statuspage
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…1#563) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
….29.0 (Ruffpuff1#565) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…uffpuff1#566) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* chore(i18n/Spanish, Mexico): Update translations for general.json * chore(i18n/Spanish, Mexico): Update translations for arguments.json * chore(i18n/Spanish, Mexico): Update translations for configuration.json * chore(i18n/Spanish, Mexico): Update translations for general.json * chore(i18n/Spanish, Mexico): Update translations for general.json * chore(i18n/Spanish, Mexico): Update translations for general.json * chore(i18n/Spanish, Mexico): Update translations for arguments.json * chore(i18n/Spanish, Mexico): Update translations for configuration.json * chore(i18n/Spanish, Mexico): Update translations for moderation.json * chore(i18n/Spanish, Mexico): Update translations for channels.json * chore(i18n/Spanish, Mexico): Update translations for contentFilters.json * chore(i18n/Spanish, Mexico): Update translations for logs.json * chore(i18n/Spanish, Mexico): Update translations for permissions.json * chore(i18n/Spanish, Mexico): Update translations for verificationLevels.json * chore(i18n/Spanish, Mexico): Update translations for globals.json * chore(i18n/Spanish, Mexico): Update translations for moderation.json * chore(i18n/Spanish, Mexico): Update translations for system.json
…1#572) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…uffpuff1#575) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
….30.0 (Ruffpuff1#574) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
* chore(i18n/Spanish, Mexico): Update translations for admin.json * chore(i18n/Spanish, Mexico): Update translations for tasks.json * chore(i18n/Spanish, Mexico): Update translations for preconditions.json * chore(i18n/Spanish, Mexico): Update translations for preconditions.json
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
….30.5 (Ruffpuff1#579) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…1#578) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…uffpuff1#580) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi
Ruffpuff1/foxxie!This is a one-off automatically generated pull request from LGTM.com 🤖. You might have heard that we’ve integrated LGTM’s underlying CodeQL analysis engine natively into GitHub. The result is GitHub code scanning!
With LGTM fully integrated into code scanning, we are focused on improving CodeQL within the native GitHub code scanning experience. In order to take advantage of current and future improvements to our analysis capabilities, we suggest you enable code scanning on your repository. Please take a look at our blog post for more information.
This pull request enables code scanning by adding an auto-generated
codeql.ymlworkflow file for GitHub Actions to your repository — take a look! Whilst we've attempted to make use of the existing configuration that you had on LGTM.com, there may be some differences in environment used to build the project. We hope that in most cases it will not require significant changes to achieve a successful analysis. Check this page for detailed documentation on how to configure a CodeQL workflow.Questions? Check out the FAQ below!
FAQ
Click here to expand the FAQ section
How often will the code scanning analysis run?
By default, code scanning will trigger a scan with the CodeQL engine on the following events:
What will this cost?
Nothing! The CodeQL engine will run inside GitHub Actions, making use of your unlimited free compute minutes for public repositories.
What types of problems does CodeQL find?
The CodeQL engine that powers GitHub code scanning is the exact same engine that powers LGTM.com. The exact set of rules has been tweaked slightly, but you should see almost exactly the same types of alerts as you were used to on LGTM.com: we’ve enabled the
security-and-qualityquery suite for you.How do I upgrade my CodeQL engine?
No need! New versions of the CodeQL analysis are constantly deployed on GitHub.com; your repository will automatically benefit from the most recently released version.
The analysis doesn’t seem to be working
If you get an error in GitHub Actions that indicates that CodeQL wasn’t able to analyze your code, please follow the instructions here to debug the analysis.
How do I disable LGTM.com?
If you have LGTM’s automatic pull request analysis enabled, then you can follow these steps to disable the LGTM pull request analysis. You don’t actually need to remove your repository from LGTM.com; it will automatically be removed in the next few months as part of the deprecation of LGTM.com (more info here).
Which source code hosting platforms does code scanning support?
GitHub code scanning is deeply integrated within GitHub itself. If you’d like to scan source code that is hosted elsewhere, we suggest that you create a mirror of that code on GitHub.
How do I know this PR is legitimate?
This PR is filed by the official LGTM.com GitHub App, in line with the deprecation timeline that was announced on the official GitHub Blog. The proposed GitHub Action workflow uses the official open source GitHub CodeQL Action. If you have any other questions or concerns, please join the discussion here in the official GitHub community!
I have another question / how do I get in touch?
Please join the discussion here to ask further questions and send us suggestions!