process: protect main and add linting, formatting and commit hooks for the backend

未关闭
#59 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
eslint, express, git, javascript, node.js

调研方向

Start by locating the backend package configuration and existing CI workflow; the issue says the React app already uses CRA's ESLint preset, but does not name backend files or test commands. Review how the backend is built and tested before estimating the lint, format, hook, and pull request template changes. Done means main has the requested protection and backend checks and hooks run as described.

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

描述

enhancement

On 9 July five pull requests (#45-#49) were opened from one branch and each was merged a minute or two after its commit, so none could be reviewed; #45 changed 239 files. The backend also has no ESLint, Prettier or Git hooks (only the React app has CRA's ESLint preset).

Suggested fix

  • Branch protection on main: pull request required, required status checks (tests), dismiss stale approvals, include administrators.
  • ESLint + Prettier for the backend, run by husky + lint-staged on pre-commit and in CI; a commit-msg hook for Conventional Commits (most history already follows it).
  • A .github/PULL_REQUEST_TEMPLATE.md asking for the linked issue and how it was tested.

Found while reviewing StudyNotion with Claude Code.

主要语言
JavaScript
星标
23
派生
8
平均合并
11 分钟
30 天内合并 PR
4

环境准备

从这里开始

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

khemssharma/StudyNotion 的其他 Issue

查看 khemssharma/StudyNotion 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

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