Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore: Enable codeql action#1454

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation

naveensrinivasan
Copy link
Contributor

This action runs GitHub's industry-leading semantic code analysis engine,CodeQL, against a repository's source code to find security vulnerabilities.https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeqlhttps://github.com/ossf/scorecard/blob/main/docs/checks.md#sastSigned-off-by: naveen <172697+naveensrinivasan@users.noreply.github.com>
@Byron
Copy link
Member

Byron commentedMay 31, 2022
edited
Loading

Thanks a lot!

Can you make it so it only runs once all tests have passed?
And could you exclude the tests from being checked as well?

@naveensrinivasan
Copy link
ContributorAuthor

Thanks a lot!

Can you make it so it only runs once all tests have passed? And could you exclude the tests from being checked as well?

I can ignore the tests folder in this PR.

Byron reacted with thumbs up emoji

@Byron
Copy link
Member

Thanks! Can you also make it so it only runs once all tests have passed?

@naveensrinivasan
Copy link
ContributorAuthor

Thanks! Can you also make it so it only runs once all tests have passed?

I can do that in the next PR.

Copy link
Member

@ByronByron left a comment

Choose a reason for hiding this comment

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

Alright, I will be waiting for exclusion of tests in this PR, so the dependency adjustment can be happening in the next one (even though I think it could happen in this one as well, but that might be a misconception).

@naveensrinivasan
Copy link
ContributorAuthor

I am going to close this for now. I can probably pick it up later. Thanks

@EliahKaganEliahKagan mentioned this pull requestDec 13, 2023
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@ByronByronByron requested changes

Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@naveensrinivasan@Byron

[8]ページ先頭

©2009-2025 Movatter.jp