Skip to content

TEST: verify lint CI catches violations (do not merge)#616

Closed
bjorkert wants to merge 3 commits intodevfrom
test/lint-failing
Closed

TEST: verify lint CI catches violations (do not merge)#616
bjorkert wants to merge 3 commits intodevfrom
test/lint-failing

Conversation

@bjorkert
Copy link
Copy Markdown
Member

Throwaway PR to verify the lint workflow added in #599 actually flags violations.

Adds LoopFollow/LintTestThrowaway.swift with intentional issues:

  • Wrong file header (not // LoopFollow\n// LintTestThrowaway.swift)
  • 8-space indentation instead of project standard
  • Double space after return

Expected: the Lint / SwiftFormat check goes red.

Do not merge. Will be closed and the branch deleted once #599 is verified.

bjorkert added 3 commits April 9, 2026 21:10
Runs swiftformat --lint in a Linux container on every PR using the
same BuildTools pin (SwiftFormat 0.56.1) and flags as the local
Scripts/swiftformat.sh, so CI stays in sync with `swift run swiftformat`
on a developer machine.

Fails the check on any violation without rewriting files — contributors
fix formatting themselves and push, rather than having CI commit back
over their branch.

BuildTools/.build is cached by Package.resolved hash to keep subsequent
runs fast.
Adds a concurrency group so rapid successive pushes to a PR branch
don't stack up multiple Lint runs — the in-progress run is cancelled
as soon as a newer commit arrives.
Base automatically changed from add_lint_workflow to dev April 26, 2026 17:59
@marionbarker
Copy link
Copy Markdown
Collaborator

Close with merge of PR #599

@bjorkert bjorkert deleted the test/lint-failing branch April 26, 2026 18:01
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.

2 participants