A CI service should be integrated with BunPro to check if all tests are still running and any SwiftLint warnings are introduced. We could also check for unused code and even do more checks later (e.g. by using Danger).
I suggest we use the Bitrise CI service which is free for open source projects. Configuration over there is done via a YAML config file which also has a grahpical editor for easier configuration. Note that the main advantage of Bitrise CI over Travis & co. is that it's mobile first. But other services might work just as well, I'm just not experienced in them. In the end the service shouldn't matters, what matters is, that we have one.
A CI service should be integrated with BunPro to check if all tests are still running and any SwiftLint warnings are introduced. We could also check for unused code and even do more checks later (e.g. by using Danger).
I suggest we use the Bitrise CI service which is free for open source projects. Configuration over there is done via a YAML config file which also has a grahpical editor for easier configuration. Note that the main advantage of Bitrise CI over Travis & co. is that it's mobile first. But other services might work just as well, I'm just not experienced in them. In the end the service shouldn't matters, what matters is, that we have one.
Here's an example of what the output on Bitrise looks like for contributors (without configuration access): https://app.bitrise.io/app/cf0587a25c78c7d4#/builds