[CI] Add ruff lint step to CI (+ optional pre-commit config)

未关闭
  • 哪里不对？
#45 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
72/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
冷清
技术栈
github-actions, python
领域
ci-cd

调研方向

The change touches requirements-dev.txt, pyproject.toml and .github/workflows/ci.yml. Start by reading the existing test job and the ci-ok gate in ci.yml, then run ruff locally against the source to see how many findings exist. Done means ruff is pinned, a [tool.ruff] section is in pyproject.toml, a lint job is added, ci-ok needs both test and lint, and CI is green.

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

描述

good first issue infra P2 quality

CI runs pytest but never lints the Python source itself (verified — no ruff/flake8/black anywhere in .github/workflows/ci.yml or pyproject.toml).

Steps:

  1. Add ruff to requirements-dev.txt (pinned)
  2. Add [tool.ruff] config to pyproject.toml — start permissive: default rules, line-length matching existing style; fix or noqa existing findings in the same PR
  3. Add a fast lint job to .github/workflows/ci.yml (single ubuntu leg) and wire it into the gate: ci-ok becomes needs: [test, lint]
  4. Optional follow-up PR: .pre-commit-config.yaml with ruff + trailing-whitespace hooks

Good first issue for someone who has set up ruff before. Keep the first PR small — config + green CI, not a style crusade.

主要语言
Python
星标
1
派生
4
平均合并
12 天 21 小时
30 天内合并 PR
1

环境准备

从这里开始

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

alphacrack/python-maithili-dsl 的其他 Issue

查看 alphacrack/python-maithili-dsl 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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