Skip to content
This repository was archived by the owner on Jan 28, 2026. It is now read-only.

Fix SwiftLint action#434

Merged
ezraberch merged 2 commits intoTokamakUI:mainfrom
ezraberch:main
Jul 28, 2021
Merged

Fix SwiftLint action#434
ezraberch merged 2 commits intoTokamakUI:mainfrom
ezraberch:main

Conversation

@ezraberch
Copy link
Member

The Github Action for SwiftLint is currently not working properly. Here is a recent example. It is not only linting the changed files. In fact, it is linting files multiple times, leading to nearly 5000 files being linted in the example. This leads to warnings being repeated multiple times.

The core issue is norio-nomura/action-swiftlint#38. Unfortunately, that bug has not been fixed in that repository, so I switched to the mayk-it/action-swift-lint fork. However, newer versions of action-swiftlint use a swift 5.4 version of SwiftLint, which will crash when linting this project (details). so I had to make my own fork which uses 5.3 (we're currently using 5.1).

Here is a run with the new version of the action.

@ezraberch ezraberch added the continuous integration Changes related to the continuous integration process label Jul 27, 2021
- uses: actions/checkout@v1
- name: Fetch base ref
run: |
git fetch --prune --no-tags --depth=1 origin +refs/heads/${{ github.base_ref }}:refs/heads/${{ github.base_ref }}
Copy link
Collaborator

Choose a reason for hiding this comment

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

Can you add a comment here that clarifies the purpose of this step?

Copy link
Collaborator

@MaxDesiatov MaxDesiatov left a comment

Choose a reason for hiding this comment

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

Thanks 👍

@ezraberch ezraberch merged commit a8c6eae into TokamakUI:main Jul 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

continuous integration Changes related to the continuous integration process

Development

Successfully merging this pull request may close these issues.

2 participants