S1.1: Monorepo scaffold with CI

未关闭 适合新手
#1 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
74/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
fastapi, github-actions, next.js, python, typescript

调研方向

阅读 .github/workflows/ci.yml 和 frontend/package.json,查看当前配置了哪些前端检查。添加自动化前端测试命令和格式检查,并将两者接入 CI。完成标准是:每个 pull request 都会与现有的前端 lint 和 build 步骤一起运行这两项检查。

由索引模型根据 Issue 内容生成。

描述

area: infra priority: P0 story

Roadmap story S1.1 · Project · Roadmap

Parent epic: E1 #97

Scope reconciliation: retains issue #1 and its existing owners; the acceptance criteria below follow the current roadmap. Previous title: Set up repository structure.

Priority: P0 · Size: M · Sprint: 0 · Milestone: M0 · Area: infra · Depends on: — · Reqs: NFR-2, NFR-9 · Status: In progress

Story: As a developer, I want a working frontend, backend, and CI from day one, so that every change is linted, built, and tested automatically.

Acceptance criteria

  • npm run dev and uv run fastapi dev start both apps locally.
  • CI runs lint, format check, tests, and build for both apps on every pull request.

Tasks

  • Scaffold the Next.js app with create-next-app
  • Scaffold the FastAPI app with uv, pytest, and Ruff, and add GET /health
  • Add CI for frontend lint/build, backend lint/format/tests, and container build/start
  • Write the root and per-app READMEs
  • Add frontend automated tests and a formatting check to satisfy the original CI criterion for both apps

Progress evidence (2026-11-08): The monorepo, READMEs, backend checks, frontend lint/build, and container build/start are committed. The original criterion also calls for frontend tests and format checking; neither gate exists in the committed frontend scripts or workflow. Evidence: PR #10, .github/workflows/ci.yml, frontend/package.json.

Audited against committed main at 0c32c57. Local, staged, and untracked work is excluded.

主要语言
Python
星标
0
派生
0
平均合并
3 小时 33 分钟
30 天内合并 PR
50

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nfiasco/Quant-Time-Machine 的其他 Issue

查看 nfiasco/Quant-Time-Machine 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。