Add MUnit to the community build

[gabro]

Question: should the project be built against Dotty 0.21 or 0.22? MUnit is currently built against 0.21, but there's an open PR that upgrades to 0.22 scalameta/munit#44 MUnit is now built against 0.22

[dottybot]

Hello, and thank you for opening this PR! 🎉

All contributors have signed the CLA, thank you! ❤️

Have an awesome day! ☀️

[gabro]

Hmm, the build is failing because the Dotty version is 0.23 but MUnit cross builds to 0.22 (it has some files in scala-0.22). What's the recommended strategy here?

[smarter]

Change your directory to scala-0 (you might need to tell sbt about that folder)

[gabro]

@smarter thanks, makes sense. I'll do it and update the submodule 👍

[gabro]

Unless I'm misinterpreting the logs, I think the CI failure is unrelated. intent tests seem to be failing, while munit tests pass.

[gabro]

Ah no, wait. I've updated intent myself by mistake. Sorry about that, I'll fix it

[gabro]

🎉 it's working now! /cc @smarter

[anatoliykmetyuk]

Thank you for the effort in porting it! All of the Dotty community projects live in forks under the dotty-staging organization – this is so that if we break the community build and need to update the projects, we can do so rapidly. I've created such a fork for MUnit: https://github.com/dotty-staging/munit

Can you point to it from your PR?

[gabro]

@anatoliykmetyuk sure thing, updated and rebased 👍

[gabro]

Ok, now the build is failing because of the recent change to the given syntax. What do you advice I do, @anatoliykmetyuk?

[anatoliykmetyuk]

@gabro I've added you to dotty-staging/munit, so you should be able to update the syntax there and reference the new commit from Dotty submodules.

[gabro]

Done 👍