Skip to content

Add Swift CodeQL workflow and fix Dependabot config#17

Open
Copilot wants to merge 1 commit intomainfrom
copilot/setup-codeql-for-swift
Open

Add Swift CodeQL workflow and fix Dependabot config#17
Copilot wants to merge 1 commit intomainfrom
copilot/setup-codeql-for-swift

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 28, 2026

CodeQL for Swift was missing, and Dependabot config failed due to an empty package ecosystem.

  • Security scanning: Add macOS CodeQL workflow that builds both iOS and macOS targets with signing disabled, using a shared CodeQL config scoping analysis to ios/ and mos/.
  • Configuration: Add .github/codeql/codeql-config.yml for Swift paths; fix .github/dependabot.yml to monitor GitHub Actions weekly.

Example (CodeQL workflow build step excerpt):

xcodebuild build \
  -project Flean.xcodeproj \
  -target Flean \
  -configuration Debug \
  -sdk iphonesimulator \
  -skipPackagePluginValidation \
  CODE_SIGNING_ALLOWED=NO \
  CODE_SIGNING_REQUIRED=NO \
  CODE_SIGN_IDENTITY=""

@kiyarose kiyarose marked this pull request as ready for review March 28, 2026 18:08
Copilot AI review requested due to automatic review settings March 28, 2026 18:08
@deepsource-io
Copy link
Copy Markdown

deepsource-io bot commented Mar 28, 2026

DeepSource Code Review

We reviewed changes in e09b771...e40a877 on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade   Security  

Reliability  

Complexity  

Hygiene  

Code Review Summary

Analyzer Status Updated (UTC) Details
PHP Mar 28, 2026 6:08p.m. Review ↗
Shell Mar 28, 2026 6:08p.m. Review ↗
JavaScript Mar 28, 2026 6:08p.m. Review ↗
Swift Mar 28, 2026 6:08p.m. Review ↗

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds Swift-focused security automation for the repo’s iOS (ios/) and macOS (mos/) Xcode projects, and fixes an invalid Dependabot configuration so automated updates run correctly.

Changes:

  • Introduces a GitHub Actions CodeQL workflow for Swift that builds both the iOS and macOS targets (with signing disabled) and uploads CodeQL results.
  • Adds a CodeQL config file scoping analysis to ios/ and mos/.
  • Fixes Dependabot config to monitor github-actions updates on a weekly cadence.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File Description
.github/workflows/codeql.yml New Swift CodeQL workflow that initializes CodeQL, builds iOS + macOS targets, and runs analysis.
.github/codeql/codeql-config.yml Scopes CodeQL analysis paths to ios and mos.
.github/dependabot.yml Replaces invalid/empty ecosystem with github-actions weekly updates.

@github-advanced-security
Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@kiyarose kiyarose disabled auto-merge March 29, 2026 02:13
@kiyarose kiyarose enabled auto-merge March 29, 2026 02:13
@kiyarose kiyarose disabled auto-merge March 29, 2026 02:13
@kiyarose kiyarose enabled auto-merge March 29, 2026 02:14
@kiyarose
Copy link
Copy Markdown
Member

Screenshot 2026-03-28 at 10 14 06 PM No clue what this means

@kiyarose
Copy link
Copy Markdown
Member

I guess we will have to wait and see when automerge eventually gets to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants