Skip to content

Create docker-image.yml cl #1

Create docker-image.yml cl

Create docker-image.yml cl #1

Workflow file for this run

# For most projects, this workflow file will not need changing; you simply need
# to commit it to your repository.
#
# You may wish to alter this file to override the set of languages analyzed,
# or to provide custom queries or build logic.
#
# ******** NOTE ********
# We have attempted to detect the languages in your repository. Please check
# the `language` matrix defined below to confirm you have the correct set of
# supported CodeQL languages.
#
name: "CodeQL Advanced"
on:
push:
branches: [ "master" ]
pull_request:
branches: [ "master" ]
schedule:
- cron: '37 13 * * 6'
jobs:
analyze:
name: Analyze (${{ matrix.language }})
# Runner size impacts CodeQL analysis time. To learn more, please see:
# - https://gh.io/recommended-hardware-resources-for-running-codeql
# - https://gh.io/supported-runners-and-hardware-resources
# - https://gh.io/using-larger-runners (GitHub.com only)
# Consider using larger runners or machines with greater resources for possible analysis time improvements.
runs-on: ${{ (matrix.language == 'swift' && 'macos-latest') || 'ubuntu-latest' }}
permissions:
# required for all workflows
security-events: write
# required to fetch internal or private CodeQL packs
packages: read
# only required for workflows in private repositories
actions: read
contents: read
strategy:
fail-fast: false
matrix:
include:
- language: c-cpp
build-mode: autobuild
- language: go
build-mode: autobuild
# CodeQL supports the following values keywords for 'language': 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'swift'
# Use `c-cpp` to analyze code written in C, C++ or both
# Use 'java-kotlin' to analyze code written in Java, Kotlin or both
# Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
# To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
# see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
# If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
# your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
steps:
- name: Checkout repository
uses: actions/checkout@v4
# Add any setup steps before running the `github/codeql-action/init` action.
# This includes steps like installing compilers or runtimes (`actions/setup-node`
# or others). This is typically only required for manual builds.
# - name: Setup runtime (example)
# uses: actions/setup-example@v1
# Initializes the CodeQL tools for scanning.
- name: Initialize CodeQL
uses: github/codeql-action/init@v3
with:
languages: ${{ matrix.language }}
build-mode: ${{ matrix.build-mode }}
# If you wish to specify custom queries, you can do so here or in a config file.
# By default, queries listed here will override any specified in a config file.
# Prefix the list here with "+" to use these queries and those in the config file.
# For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
# queries: security-extended,security-and-quality
# If the analyze step fails for one of the languages you are analyzing with
# "We were unable to automatically build your code", modify the matrix above
# to set the build mode to "manual" for that language. Then modify this step
# to build your code.
# ℹ️ Command-line programs to run using the OS shell.
# 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
- if: matrix.build-mode == 'manual'
shell: bash
run: |
echo 'If you are using a "manual" build mode for one or more of the' \
'languages you are analyzing, replace this with the commands to build' \
'your code, for example:'
echo ' make bootstrap'
echo ' make release'
exit 1
- name: Perform CodeQL Analysis
uses: github/codeql-action/analyze@v3
with:
category: "/language:${{matrix.language}}" - नाम: सेटअप .NET कोर SDK

Check failure on line 100 in .github/workflows/codeql.yml

View workflow run for this annotation

GitHub Actions / .github/workflows/codeql.yml

Invalid workflow file

You have an error in your yaml syntax on line 100
उपयोग: actions/[email protected]
साथ:
# उपयोग करने के लिए वैकल्पिक SDK संस्करण। यदि उपलब्ध नहीं है, तो उपलब्ध होने पर global.json संस्करण स्थापित किया जाएगा। उदाहरण: 2.2.104, 3.1, 3.1.x, 3.x, 6.0.2xx
dotnet-version: # वैकल्पिक
# निर्माण की वैकल्पिक गुणवत्ता। संभावित मान हैं: दैनिक, हस्ताक्षरित, मान्य, पूर्वावलोकन, जीए।
dotnet-quality: # वैकल्पिक
# वैकल्पिक global.json स्थान, यदि आपका global.json रेपो के मूल में स्थित नहीं है.
ग्लोबल-json-फ़ाइल: # वैकल्पिक
# वैकल्पिक पैकेज स्रोत जिसके लिए प्रमाणीकरण सेट अप करना है। रेपो के रूट में किसी भी मौजूदा NuGet.config से परामर्श करेगा और ClearTextPassword के रूप में NUGET_AUTH_TOKEN पर्यावरण चर का उपयोग करके एक अस्थायी NuGet.config प्रदान करेगा।
स्रोत-url: # वैकल्पिक
# वर्तमान रिपॉजिटरी के स्वामी के अलावा GitHub पैकेज रजिस्ट्री संगठनों/उपयोगकर्ताओं से पैकेज का उपयोग करने के लिए वैकल्पिक स्वामी। केवल तभी उपयोग किया जाता है जब स्रोत-url में GPR URL भी प्रदान किया गया हो
स्वामी: # वैकल्पिक
# वैकल्पिक NuGet.config स्थान, यदि आपका NuGet.config रेपो के मूल में स्थित नहीं है।
कॉन्फ़िगरेशन फ़ाइल: # वैकल्पिक
# NuGet ग्लोबल-पैकेज फ़ोल्डर की कैशिंग सक्षम करने के लिए वैकल्पिक इनपुट
कैश: # वैकल्पिक
# निर्भरता फ़ाइल का पथ निर्दिष्ट करने के लिए उपयोग किया जाता है: packages.lock.json. एकाधिक निर्भरताओं को कैश करने के लिए वाइल्डकार्ड या फ़ाइल नामों की सूची का समर्थन करता है.
कैश-निर्भरता-पथ: # वैकल्पिक