This should make it possible to have rust-ci-conf as a remote you merge
from.

Bumps [codecov/codecov-action](https://github.com/codecov/codecov-action) from 2 to 3.
- [Release notes](https://github.com/codecov/codecov-action/releases)
- [Changelog](https://github.com/codecov/codecov-action/blob/main/CHANGELOG.md)
- [Commits](codecov/codecov-action@v2...v3)

---
updated-dependencies:
- dependency-name: codecov/codecov-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>

…odecov-action-3

Bump codecov/codecov-action from 2 to 3

See actions-rs/toolchain#216

Given that that project is unmaintained.

actions-rs/toolchain#216

See tokio-rs/tokio#5072

`cargo test --all-features` does not run doc-tests. For more information
see rust-lang/cargo#6669.

Fixes Peternator7#8

This repo contains a reasonable stub of CI workflows and configuration
for rust crates. It includes config for dependabot, codecov.io, and
workflows for checking format and clippy, testing on multiple OSes,
determining the minimum supported rust version, checking for problems
with minimal versions, and runs scheduled tasks to ensure that new rust
versions and dependencies do not break this crate.

This is a merge using the --allow-unrelated-histories flag, that brings
in the entire history of that repo. This enables the CI to be later
merged if configuration changes are made upstream.

test_phf feature is incompatible with 1.32 as siphasher crate does not build

We do not have unsafe code in strum, so this is not necessary

no-std checks fail to build textwrap, which is a required dependency of structopts

Before this change, attempting to build strum_no_std would include std in the default features of strum, which would prevent it building