ci: remove CodeQL workflow file #529
Merged
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
Signed-off-by: Lin Yang <[email protected]>
reaver-flomesh
added
area/CI
reaver-flomesh
requested review from
cybwan,
addozhang,
naqvis and
caishu97
as code owners
reaver-flomesh
added
the
needs-backport
✅ PR Title Formatted CorrectlyThe title of this PR has been updated to match the correct format. Thank you! |
github-actions bot
pushed a commit
that referenced
this pull request
Dec 19, 2024
Signed-off-by: Lin Yang <[email protected]> (cherry picked from commit 64bf5b2)
|
Successfully created backport PR for |
reaver-flomesh
added a commit
that referenced
this pull request
Dec 19, 2024
ci: remove CodeQL workflow file (#529) Signed-off-by: Lin Yang <[email protected]> (cherry picked from commit 64bf5b2)
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.
Description:
Testing done:
Affected area:
Please answer the following questions with yes/no.
Does this change contain code from or inspired by another project?
Is this a breaking change?
Has documentation corresponding to this change been updated in the fsm-docs repo (if applicable)?