Migrate to github actions

[danieleades]

just wanted to check whether there was any appetite for migrating from circle CI to github actions?

[marshallpierce]

It's not on my to-do list, though I'm not categorically rejecting it -- it's unclear to me what the net benefits of switching would be, and I view tying a project too strongly to GitHub as a negative in general. That's why other than old projects like this I do my OSS work on bitbucket.

[danieleades]

I get that. The advantages are the same as the disadvantages- namely, tighter integration with GitHub.

You also get slightly better community support (in the form of reusable GitHub actions), and possibly easier onboarding for would be contributors

[marshallpierce]

Another of my concerns about actions is the supply chain security aspect. If I'm letting someone else's code participate in the build, that's a risk. There's certainly a risk in rustup'ing a toolchain as well, but it's harder to surgically affect a build via cooperation with rustup's CDN than it is in an action.

[danieleades]

Fair enough

[tcharding]

Would it be useful to host this project on bitbucket and mirror it here on github? Then we could use github actions here and other CI infrastructure on bitbucket and then we could do #98.

[marshallpierce]

I do like avoiding the GitHub hegemony to minimize the collateral damage when GitHub inevitably rug-pulls, which is why most of my projects live on BitBucket, but I think mirroring is more hassle than it's worth to maintain philosophical purity. See #98 (comment) about GHA for fuzzing.