jbampton commented on code in PR #11300:
URL: https://github.com/apache/cloudstack/pull/11300#discussion_r2352998006


##########
.github/workflows/codeql-analysis.yml:
##########
@@ -0,0 +1,48 @@
+# Licensed to the Apache Software Foundation (ASF) under one
+# or more contributor license agreements.  See the NOTICE file
+# distributed with this work for additional information
+# regarding copyright ownership.  The ASF licenses this file
+# to you under the Apache License, Version 2.0 (the
+# "License"); you may not use this file except in compliance
+# with the License.  You may obtain a copy of the License at
+#
+#   http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing,
+# software distributed under the License is distributed on an
+# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+# KIND, either express or implied.  See the License for the
+# specific language governing permissions and limitations
+# under the License.
+
+name: CodeQL Analysis
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+permissions:
+  actions: read
+  contents: read
+  security-events: write
+jobs:
+  codeql:
+    name: CodeQL
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        language: ["actions"]

Review Comment:
   
   > Do we need to add more languages here?
   
   Let us get this PR merged first before we add more languages and checks.
   
   For example if we add the Java language to the matrix we may also need to 
implement "paths" or only run the Java CodeQL check when certain files change.  
These checks can sometimes take a while to run on the CI.
   
   Also it is probably best to separate each language that we want to check 
into its own CodeQL workflow file and add all the "paths". For example:
   
   - java-codeql-analysis.yml
   - python-codeql-analysis.yml
   - actions-codeql-analysis.yml
   - etc
   
   Using separate CodeQL workflow files for each language in a multi-language 
repository allows for tailored analysis and build processes. This approach is 
particularly useful when languages have different build requirements or when 
you want to apply specific queries or configurations to individual languages.
   
   



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to