Closed mkantor closed 4 years ago
I wasn't sure exactly what you wanted to check in CI; this only runs the tests.
In my other repository I also have these jobs:
format:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- run: cargo fmt --all -- --check
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- run: cargo clippy -- -D warnings
Let me know if you'd like either/both of those here!
Oh, and you may have to enable actions in your repository settings as well.
Thanks :+1: a lot, I will merge, (and) maybe modify/extend it soon.
(I plan to put multiple repos on Github action since a while but didn't find yet the time for it).
While evaluating this crate I saw #10. I had recently configured CI for another Rust project using GitHub Actions and was pleasantly surprised by how easy it was, so I figured I'd propose a similar setup for
vec1
. Here's an example run.@rustonaut you suggested Travis CI in #10. If you prefer that don't hesitate to close this.