Fix typo of Swift Playground at CommentSpacingRule.swift

[lamtrinhdev]

Correct typo of Swift Playground at CommentSpacingRule.swift , it appears in production at https://realm.github.io/SwiftLint/comment_spacing.html .

[SwiftLintBot]

	1 Warning
⚠️	If this is a user-facing change, please include a CHANGELOG entry to credit yourself! You can find it at CHANGELOG.md.

	17 Messages
📖	Linting Aerial with this PR took 0.25s vs 0.23s on main (8% slower)
📖	Linting Alamofire with this PR took 0.27s vs 0.27s on main (0% slower)
📖	Linting Brave with this PR took 1.32s vs 1.31s on main (0% slower)
📖	Linting DuckDuckGo with this PR took 0.77s vs 0.77s on main (0% slower)
📖	Linting Firefox with this PR took 2.13s vs 2.13s on main (0% slower)
📖	Linting Kickstarter with this PR took 1.46s vs 1.48s on main (1% faster)
📖	Linting Moya with this PR took 0.15s vs 0.15s on main (0% slower)
📖	Linting NetNewsWire with this PR took 0.51s vs 0.5s on main (2% slower)
📖	Linting Nimble with this PR took 0.18s vs 0.18s on main (0% slower)
📖	Linting PocketCasts with this PR took 1.3s vs 1.27s on main (2% slower)
📖	Linting Quick with this PR took 0.13s vs 0.13s on main (0% slower)
📖	Linting Realm with this PR took 0.86s vs 0.86s on main (0% slower)
📖	Linting Sourcery with this PR took 0.46s vs 0.48s on main (4% faster)
📖	Linting Swift with this PR took 0.81s vs 0.81s on main (0% slower)
📖	Linting VLC with this PR took 0.3s vs 0.3s on main (0% slower)
📖	Linting Wire with this PR took 3.24s vs 3.25s on main (0% faster)
📖	Linting WordPress with this PR took 2.15s vs 2.14s on main (0% slower)

Here's an example of your CHANGELOG entry:

* Fix typo of Swift Playground at CommentSpacingRule.swift.  
  [lamtrinhdev](https://github.com/lamtrinhdev)
  [#issue_number](https://github.com/realm/SwiftLint/issues/issue_number)

note: There are two invisible spaces after the entry's text.

Generated by 🚫 Danger

[SimplyDanny]

Thanks!

[lamtrinhdev]

Dear @SimplyDanny ,

We have some failing cases. Could you help me to check it?

Thanks,
Lam

[alex-taffe]

It seems like the main branch is currently broken for what that's worth

[mildm8nnered]

It seems like the main branch is currently broken for what that's worth

I see it - just putting up a PR to fix that - @SimplyDanny

[mildm8nnered]

PR at #5695, which seems to failing :-(

[lamtrinhdev]

How can the PR #5694 build successful for 12 tasks?

[SimplyDanny]

How can the PR #5694 build successful for 12 tasks?

It is based on b9f3843 which is the commit before the compile issues were introduced.

PR at #5695, which seems to failing :-(

It only failed OSS check. That's because OSS check does not only build the PR branch but also main (which still had the issues).

I just merged it and so main should be good again now.

@mildm8nnered: Thank you for the fix!
@lamtrinhdev: Please rebase your PR onto main. Build ought to be successful again.

[alex-taffe]

Yeah I intentionally rewound mine by 1 commit

[lamtrinhdev]

Thank you for your support, @mildm8nnered , @SimplyDanny , @alex-taffe . Let me update to date my branch.

[SimplyDanny]

You should rebase your branch instead of merging main into it. Danger doesn't like merges. 😉

[lamtrinhdev]

I got it. Thank you for your support @SimplyDanny .