doubleo7/.forgejo/workflows/ci.yml

36 lines
697 B
YAML
Raw Permalink Normal View History

Extract swear_cleanup to its own repo, flatten deep_research to root deep_research is the only project this repo is meant to showcase, so the Cargo workspace wrapping it and an unrelated side project no longer earns its keep: - swear_cleanup moved to a new standalone local repo (~/dev/swear_cleanup, not pushed anywhere) via `git subtree split`, with its pre-workspace- split history (when it lived at src/swear_cleanup/ in a single shared crate) spliced onto its post-split history rather than starting from a single flattened snapshot. FINDINGS.md, which was sitting at this repo's root but was actually swear_cleanup's own build log, went with it. - deep_research/{src,Cargo.toml,README.md,docs} moved to the repo root; the [workspace] table collapsed into a plain [package] manifest with dependency versions inlined from the old [workspace.dependencies]. - Cargo.toml keeps an explicit empty [workspace] table (not just omitted) so that checking this repo out as a nested git worktree — this project's own normal workflow — can't accidentally inherit a stale ancestor directory's workspace manifest, which is exactly what broke the build while testing this change from a worktree. - .forgejo/workflows/deep_research-ci.yml -> ci.yml, dropping the now- meaningless -p deep_research scoping and path filters (redundant when it's the only thing in the repo). - README.md and docs/case-study.md updated for the flattened commands (cargo run/test with no -p flag); their relative links to each other and to src/ were already correct since both moved together. Verified: cargo build/test/clippy/fmt all clean from the new repo root.
2026-08-18 11:43:26 +00:00
name: CI
on:
push:
branches: [master]
pull_request:
jobs:
test:
runs-on: rust-ci
steps:
- uses: actions/checkout@v4
- name: Cache cargo registry and build artifacts
uses: actions/cache@v4
with:
path: |
~/.cargo/registry
~/.cargo/git
target
key: cargo-${{ runner.os }}-${{ hashFiles('Cargo.lock') }}
restore-keys: |
cargo-${{ runner.os }}-
- name: Check formatting
Extract swear_cleanup to its own repo, flatten deep_research to root deep_research is the only project this repo is meant to showcase, so the Cargo workspace wrapping it and an unrelated side project no longer earns its keep: - swear_cleanup moved to a new standalone local repo (~/dev/swear_cleanup, not pushed anywhere) via `git subtree split`, with its pre-workspace- split history (when it lived at src/swear_cleanup/ in a single shared crate) spliced onto its post-split history rather than starting from a single flattened snapshot. FINDINGS.md, which was sitting at this repo's root but was actually swear_cleanup's own build log, went with it. - deep_research/{src,Cargo.toml,README.md,docs} moved to the repo root; the [workspace] table collapsed into a plain [package] manifest with dependency versions inlined from the old [workspace.dependencies]. - Cargo.toml keeps an explicit empty [workspace] table (not just omitted) so that checking this repo out as a nested git worktree — this project's own normal workflow — can't accidentally inherit a stale ancestor directory's workspace manifest, which is exactly what broke the build while testing this change from a worktree. - .forgejo/workflows/deep_research-ci.yml -> ci.yml, dropping the now- meaningless -p deep_research scoping and path filters (redundant when it's the only thing in the repo). - README.md and docs/case-study.md updated for the flattened commands (cargo run/test with no -p flag); their relative links to each other and to src/ were already correct since both moved together. Verified: cargo build/test/clippy/fmt all clean from the new repo root.
2026-08-18 11:43:26 +00:00
run: cargo fmt -- --check
- name: Lint
Extract swear_cleanup to its own repo, flatten deep_research to root deep_research is the only project this repo is meant to showcase, so the Cargo workspace wrapping it and an unrelated side project no longer earns its keep: - swear_cleanup moved to a new standalone local repo (~/dev/swear_cleanup, not pushed anywhere) via `git subtree split`, with its pre-workspace- split history (when it lived at src/swear_cleanup/ in a single shared crate) spliced onto its post-split history rather than starting from a single flattened snapshot. FINDINGS.md, which was sitting at this repo's root but was actually swear_cleanup's own build log, went with it. - deep_research/{src,Cargo.toml,README.md,docs} moved to the repo root; the [workspace] table collapsed into a plain [package] manifest with dependency versions inlined from the old [workspace.dependencies]. - Cargo.toml keeps an explicit empty [workspace] table (not just omitted) so that checking this repo out as a nested git worktree — this project's own normal workflow — can't accidentally inherit a stale ancestor directory's workspace manifest, which is exactly what broke the build while testing this change from a worktree. - .forgejo/workflows/deep_research-ci.yml -> ci.yml, dropping the now- meaningless -p deep_research scoping and path filters (redundant when it's the only thing in the repo). - README.md and docs/case-study.md updated for the flattened commands (cargo run/test with no -p flag); their relative links to each other and to src/ were already correct since both moved together. Verified: cargo build/test/clippy/fmt all clean from the new repo root.
2026-08-18 11:43:26 +00:00
run: cargo clippy --all-targets -- -D warnings
- name: Build
Extract swear_cleanup to its own repo, flatten deep_research to root deep_research is the only project this repo is meant to showcase, so the Cargo workspace wrapping it and an unrelated side project no longer earns its keep: - swear_cleanup moved to a new standalone local repo (~/dev/swear_cleanup, not pushed anywhere) via `git subtree split`, with its pre-workspace- split history (when it lived at src/swear_cleanup/ in a single shared crate) spliced onto its post-split history rather than starting from a single flattened snapshot. FINDINGS.md, which was sitting at this repo's root but was actually swear_cleanup's own build log, went with it. - deep_research/{src,Cargo.toml,README.md,docs} moved to the repo root; the [workspace] table collapsed into a plain [package] manifest with dependency versions inlined from the old [workspace.dependencies]. - Cargo.toml keeps an explicit empty [workspace] table (not just omitted) so that checking this repo out as a nested git worktree — this project's own normal workflow — can't accidentally inherit a stale ancestor directory's workspace manifest, which is exactly what broke the build while testing this change from a worktree. - .forgejo/workflows/deep_research-ci.yml -> ci.yml, dropping the now- meaningless -p deep_research scoping and path filters (redundant when it's the only thing in the repo). - README.md and docs/case-study.md updated for the flattened commands (cargo run/test with no -p flag); their relative links to each other and to src/ were already correct since both moved together. Verified: cargo build/test/clippy/fmt all clean from the new repo root.
2026-08-18 11:43:26 +00:00
run: cargo build
- name: Test
Extract swear_cleanup to its own repo, flatten deep_research to root deep_research is the only project this repo is meant to showcase, so the Cargo workspace wrapping it and an unrelated side project no longer earns its keep: - swear_cleanup moved to a new standalone local repo (~/dev/swear_cleanup, not pushed anywhere) via `git subtree split`, with its pre-workspace- split history (when it lived at src/swear_cleanup/ in a single shared crate) spliced onto its post-split history rather than starting from a single flattened snapshot. FINDINGS.md, which was sitting at this repo's root but was actually swear_cleanup's own build log, went with it. - deep_research/{src,Cargo.toml,README.md,docs} moved to the repo root; the [workspace] table collapsed into a plain [package] manifest with dependency versions inlined from the old [workspace.dependencies]. - Cargo.toml keeps an explicit empty [workspace] table (not just omitted) so that checking this repo out as a nested git worktree — this project's own normal workflow — can't accidentally inherit a stale ancestor directory's workspace manifest, which is exactly what broke the build while testing this change from a worktree. - .forgejo/workflows/deep_research-ci.yml -> ci.yml, dropping the now- meaningless -p deep_research scoping and path filters (redundant when it's the only thing in the repo). - README.md and docs/case-study.md updated for the flattened commands (cargo run/test with no -p flag); their relative links to each other and to src/ were already correct since both moved together. Verified: cargo build/test/clippy/fmt all clean from the new repo root.
2026-08-18 11:43:26 +00:00
run: cargo test