Missing CI

[sameo]

This project has no CI, shame on us.

We want to implement a github actions based CI that would:

• Build the project, with the stable, beta and nightly toolchains
• Run all unit and integration tests
• Run cargo clippy
• Run cargo fmt

for each pending PR.

Any of this step failing should prevent the PR to be merged.

[thomasgouveia]

See PR #10

@sameo , I do not understand why we have to build with beta and nightly toolchains ?

Also, do we have to create a release after each merge on main to allow people to download a binary ?

[sameo]

@thomasgouveia

See PR #10

@sameo , I do not understand why we have to build with beta and nightly toolchains ?

Because there is no reason our code would not build with those toolchains, and this would let us anticipate any breakage when we move to newer toolchains.

Also, do we have to create a release after each merge on main to allow people to download a binary ?

No, we should only generate a release when we tag the main branch (a.k.a. a release).