Something went wrong. Try again.
A minimal atproto Personal Data Server, on SQLite. github.com/eth0net/manapds
Something went wrong. Try again.
1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374name: CI
on: push: branches: [main] pull_request:
env: CARGO_TERM_COLOR: always RUSTFLAGS: -D warnings
jobs: test: name: test (${{ matrix.os }}) runs-on: ${{ matrix.os }} strategy: fail-fast: false matrix: # No Windows: an account's files sit under its DID, and a DID has # colons in it, which Windows will not have in a path. os: [ubuntu-latest, macos-latest] steps: - uses: actions/checkout@v7 - uses: dtolnay/rust-toolchain@stable - uses: Swatinem/rust-cache@v2 - run: cargo test --locked --all-targets
lint: name: fmt and clippy runs-on: ubuntu-latest steps: - uses: actions/checkout@v7 - uses: dtolnay/rust-toolchain@stable with: components: rustfmt, clippy - uses: Swatinem/rust-cache@v2 - run: cargo fmt --all --check - run: cargo clippy --locked --all-targets --all-features
msrv: name: minimum supported rust version runs-on: ubuntu-latest steps: - uses: actions/checkout@v7 # Keep in step with rust-version in Cargo.toml. - uses: dtolnay/rust-toolchain@1.98 - uses: Swatinem/rust-cache@v2 - run: cargo check --locked
typos: name: spelling runs-on: ubuntu-latest steps: - uses: actions/checkout@v7 # Reads typos.toml, so the repo's `locale` applies here too. - uses: crate-ci/typos@v1.50.2
deny: name: supply chain runs-on: ubuntu-latest steps: - uses: actions/checkout@v7 # Advisories, licenses, duplicate versions and crate sources. Configured # in deny.toml, which says what each check is for. - uses: EmbarkStudios/cargo-deny-action@v2 with: command: check # Escalates unmaintained notices, yanked versions and unused allow # entries to match the -D warnings the other jobs run under. The # advisory database moves on its own, so this can fail on a tree that # has not changed. That is the point; the escape hatch is an `ignore` # entry in deny.toml with a reason. command-arguments: --deny warnings