Skip to content

chore: add SwiftLint config, build CI, unpin Xcode in CodeQL#6

Merged
Krivoblotsky merged 1 commit intodevelopfrom
chore/tooling-and-ci
May 1, 2026
Merged

chore: add SwiftLint config, build CI, unpin Xcode in CodeQL#6
Krivoblotsky merged 1 commit intodevelopfrom
chore/tooling-and-ci

Conversation

@Krivoblotsky
Copy link
Copy Markdown
Contributor

Summary

Brings the project up to a contributor-friendly tooling baseline.

  • .swiftlint.yml — pragmatic ruleset: line length 140 (200 error), opt-in best-practice rules (empty_count, explicit_init, first_where, last_where, contains_over_first_not_nil, sorted_first_last), exclude Xcode build artefacts.
  • .github/workflows/build.yml — new workflow that builds the Xcode project on every push/PR to develop and main. Uses maxim-lobanov/setup-xcode@v1 with latest-stable and xcbeautify for clean logs.
  • .github/workflows/codeql.yml — replace the hardcoded sudo xcode-select -s /Applications/Xcode_16.1.app step with the same setup-xcode@v1 action so the workflow doesn't break the next time the GitHub runner image moves on.

Type of Change

  • CI / tooling

Test plan

  • CI Build workflow runs and succeeds against this PR
  • CodeQL workflow runs against this PR with the new Xcode selector
  • Run swiftlint lint locally and confirm no errors on the existing source tree

🤖 Generated with Claude Code

- .swiftlint.yml: pragmatic ruleset (line length 140, opt-in best
  practice rules, exclude Xcode project artefacts).
- .github/workflows/build.yml: build the project on every PR/push to
  develop and main so broken builds are caught before merge.
- codeql.yml: replace hardcoded Xcode 16.1 path with
  maxim-lobanov/setup-xcode@v1 + latest-stable so the workflow does
  not break when GitHub runners upgrade.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@Krivoblotsky Krivoblotsky merged commit bf52ac6 into develop May 1, 2026
1 check passed
@Krivoblotsky Krivoblotsky deleted the chore/tooling-and-ci branch May 1, 2026 16:33
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.

1 participant