Create a standalone repo for the SwiftLint plugins

[BrentMifsud]

New Issue Checklist

• I've Updated SwiftLint to the latest version.
• I've searched for existing GitHub issues.

Feature or Enhancement Proposal

With the addition of macros to the swift language, many dependencies now rely on swift syntax. Some of which conflict with the version of swift syntax that SwiftLint is using.

Here is an example issue: lukepistrol/SFSymbolsMacro#4

It would be nice if there was an official SwiftLint plugin repo, rather than having to rely on third parties to make one (like mentioned in the issue I linked above)

[SimplyDanny]

It would be nice if there was an official SwiftLint plugin repo, rather than having to rely on third parties to make one (like mentioned in the issue I linked above)

This is an interesting point. What would you call a "third party" in an open source project?

SwiftLint is not managed by a company but by people maintaining it as a hobby. If you rely on OSS, you rely on the people defining it. In this specific case, that's me providing SwiftLintPlugins as a binary version of the plugins. The repository is fully synced with the main SwiftLint repository and its releases. You actually won't get something more "official" right now. At least I don't know who you ask to provide that.

[BrentMifsud]

It would be nice if there was an official SwiftLint plugin repo, rather than having to rely on third parties to make one (like mentioned in the issue I linked above)

This is an interesting point. What would you call a "third party" in an open source project?

SwiftLint is not managed by a company but by people maintaining it as a hobby. If you rely on OSS, you rely on the people defining it. In this specific case, that's me providing SwiftLintPlugins as a binary version of the plugins. The repository is fully synced with the main SwiftLint repository and its releases. You actually won't get something more "official" right now. At least I don't know who you ask to provide that.

Is there any automation in place to ensure that the SwiftLintPlugins repo does not become out of sync with the main swiftlint repo?

I guess that's my only hesitation.

[SimplyDanny]

There is one workflow that syncs the Plugins directory whenever there is a change on any of the files in there. Another workflow creates a matching release in SwiftLintPlugins with the data used to create a release in SwiftLint. With that, there is nothing to do in the plugin repository itself. It's basically a mirror. Only an outdated token has the potential to cause trouble.

[BrentMifsud]

Awesome. Thanks for the info.