# A CodeQL query for the UA .NET Standard project name: "CodeQL" on: # master is analyzed by the daily schedule below rather than on every push. # Each analysis takes about three hours, and with a per-branch concurrency # group most push runs on master were cancelled by the next merge before they # finished (49 of 76 over two weeks in October 2026), burning runner time # without ever uploading a result. A daily run always completes, and it is # the base-branch analysis that pull request results are compared against. # The other long-lived branches change rarely and keep their push trigger. push: branches: [ master378, release/*, develop/* ] pull_request: # master is not in the push list above; the schedule provides its base # analysis. branches: [ master, main, master378 ] paths: - '**.cs' schedule: - cron: '30 6 * * *' workflow_dispatch: permissions: actions: read contents: read packages: read security-events: write # A superseded pull request analysis is cancelled. A push or scheduled run is # never cancelled, so a branch analysis always finishes and uploads; a newer # one queues behind it, replacing any run already waiting. concurrency: group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }} cancel-in-progress: ${{ github.event_name == 'pull_request' }} jobs: analyze: name: Analyze # Linux: only net10.0 is built (see below), so the extracted sources are the # same as on Windows. On windows-2025 the traced build alone took 70 minutes, # against 12 for the build-UA net10.0 (linux) leg of buildandtest.yml, which # also keeps UA.slnx building on Linux. runs-on: ubuntu-latest strategy: fail-fast: false matrix: language: [ 'csharp' ] # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python' ] # Learn more: # https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#changing-the-languages-that-are-analyzed steps: - name: Checkout repository uses: actions/checkout@v7 # Initializes the CodeQL tools for scanning. - name: Initialize CodeQL uses: github/codeql-action/init@v4 with: languages: ${{ matrix.language }} # 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. # queries: ./path/to/local/query, your-org/your-repo/queries@main - name: Set up .NET uses: actions/setup-dotnet@v6 with: dotnet-version: '10.0.401' # https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages#c-compiler-flags-injected-by-codeql-for-manual-builds # # CustomTestTarget pins the build to a single target framework (see # targets.props). A default build multi-targets up to six frameworks, so # CodeQL would extract every source file - and every source generated file, # which EmitCompilerGeneratedFiles materializes on disk and which alone is # tens of megabytes per project - once per framework. That duplication grew # the database until "codeql database interpret-results" ran out of memory # on the hosted runner. Analyzing one framework covers the same sources # once and keeps the database within the runner's memory budget. - name: Build Solution run: | dotnet build "UA.slnx" -c Release -p:CustomTestTarget=net10.0 -p:UseSharedCompilation=false -p:EmitCompilerGeneratedFiles=true - name: Perform CodeQL Analysis uses: github/codeql-action/analyze@v4 with: # Interpreting results in parallel keeps a result set and its source # snippets in memory per thread. Two threads bound the peak memory of # the step that previously failed with an out of memory error. threads: 2