Thomas Eizinger
Thomas Eizinger
See https://github.com/thomaseizinger/github-action-gitflow-release-workflow/pull/43#issuecomment-1247582138.
Our release workflow is currently broken: https://github.com/thomaseizinger/github-action-gitflow-release-workflow/actions/runs/3065049502/jobs/4948757562#step:9:17
Currently, depending on `emerald-vault-core` brings in a lot of dependencies, like `librocksdb-sys` which takes a long time to compile. In addition, the shared library `libusb-1.0` needs to be installed in...
Tried to use `emerald_vault_core` without default features and it doesn't compile because the `extern crate reqwest` statement is not gated with the `http` feature.
First all, thanks for this great editor! It has been my default editor for a while now and I really like it :) One thing that I am missing is...
As per title `cargo test --all-targets` does not run the doc tests on a crate. This is very surprising behaviour. I found [this](https://github.com/rust-lang/cargo/pull/4592#issuecomment-338409476) and it looks like running doc tests...
I'd like to reboot https://github.com/ohmyzsh/ohmyzsh/issues/8767 and get this properly upstreamed here. Would you accept a contribution for this? Should this be configurable?
Previously, each synthetic project got its own target directory. That results in a lot of recompilation. Because the entire workspace of `cargo semver-checks` is within the original projects `target` directory,...