Skip to content

docs: update README with new deployment steps and reorganize contribution guide#24

Closed
akaBoyLovesToCode wants to merge 2 commits intoembyplus:mainfrom
akaBoyLovesToCode:main
Closed

docs: update README with new deployment steps and reorganize contribution guide#24
akaBoyLovesToCode wants to merge 2 commits intoembyplus:mainfrom
akaBoyLovesToCode:main

Conversation

@akaBoyLovesToCode
Copy link
Contributor

@akaBoyLovesToCode akaBoyLovesToCode commented Feb 15, 2025

This PR includes two documentation-related changes:

Update README Content:

  • Updated the README with new deployment steps, replacing pip with uv commands (uv sync and uv run) for environment setup and bot execution.
  • Enhanced the overall layout and formatting of the README for improved clarity.
  • Added an English version of the README to broaden accessibility.
  • Moved the contribution guide to a separate CONTRIBUTING.md file for better organization.
  • Integrated various badges (e.g., license, Python version, code quality, and Ruff) to provide quick access to project metrics.

These updates aim to streamline the deployment process and improve the documentation structure, making it more user-friendly and maintainable.

好的,这是翻译成中文的 pull request 总结:

Sourcery 提供的总结

更新 README 中的部署说明以使用 uv,并创建一个新的 CONTRIBUTING.md 文件。

文档:

  • 更新 README,使用 uv 命令代替 pip 的新部署说明。
  • 添加 README 的英文版本。
  • 将贡献指南移至单独的 CONTRIBUTING.md 文件。
  • 向 README 添加各种徽章,包括许可证、Python 版本、代码质量和 Ruff。
  • 改进 README 的整体布局和格式。
  • CONTRIBUTING.md 中创建一个贡献指南,其中包含提交消息、数据库和 API 更改、pull request 的指南,以及支持的提交类型列表。
Original summary in English

Summary by Sourcery

Update the deployment instructions in the README to use uv and create a new CONTRIBUTING.md file.

Documentation:

  • Update the README with new deployment instructions using uv commands instead of pip.
  • Add an English version of the README.
  • Move the contribution guidelines to a separate CONTRIBUTING.md file.
  • Add various badges to the README, including license, Python version, code quality, and Ruff.
  • Improve the overall layout and formatting of the README.
  • Create a contribution guide in CONTRIBUTING.md with guidelines for commit messages, database and API changes, pull requests, and a list of supported commit types

…ibution guide

- Replaced `pip` with `uv` for deployment and added `uv sync` and `uv run` commands for environment setup and bot execution
- Enhanced README layout with improved clarity and formatting
- Added English version of the README
- Moved the contribution guide to `CONTRIBUTING.md` for better organization
- Added badges for various services such as license, Python version, code quality, and ruff
@sourcery-ai
Copy link

sourcery-ai bot commented Feb 15, 2025

## Sourcery 评审者指南

此 Pull Request 使用 `uv` 更新了 README 中的新部署步骤,并将贡献指南重组到一个单独的文件中。它还增强了 README 的布局,并添加了项目指标的徽章。

#### 新部署步骤的流程图

```mermaid
graph LR
    A[克隆仓库] --> B(复制并编辑环境变量文件)
    B --> C{使用 uv sync 同步依赖环境}
    C --> D{使用 uv run app.py 运行机器人}

文件级别变更

变更 详情 文件
使用 uv 而不是 pip 更新了 README 中的新部署步骤。
  • pip sync 替换为 uv sync
  • pip run 替换为 uv run
README.md
增强了 README 的布局和格式,以提高清晰度,并添加了项目指标的各种徽章。
  • 改进了 README 的整体布局和格式。
  • 添加了许可证、Python 版本、代码质量和 Ruff 的徽章。
  • 添加了 uv、pre-commit、pyright 和 ruff 的徽章。
README.md
将贡献指南移动到单独的 CONTRIBUTING.md 文件中。
  • 创建了一个新的 CONTRIBUTING.md 文件。
  • README.md 中删除了贡献指南。
README.md
CONTRIBUTING.md

提示和命令

与 Sourcery 互动

  • 触发新的审查: 在 Pull Request 上评论 @sourcery-ai review
  • 继续讨论: 直接回复 Sourcery 的审查评论。
  • 从审查评论生成 GitHub issue: 通过回复审查评论,要求 Sourcery 从审查评论创建一个 issue。您也可以回复审查评论并使用 @sourcery-ai issue 从中创建一个 issue。
  • 生成 Pull Request 标题: 在 Pull Request 标题中的任何位置写入 @sourcery-ai,以随时生成标题。您也可以在 Pull Request 上评论 @sourcery-ai title 以随时(重新)生成标题。
  • 生成 Pull Request 摘要: 在 Pull Request 正文中的任何位置写入 @sourcery-ai summary,以随时在您想要的位置生成 PR 摘要。您也可以在 Pull Request 上评论 @sourcery-ai summary 以随时(重新)生成摘要。
  • 生成评审者指南: 在 Pull Request 上评论 @sourcery-ai guide 以随时(重新)生成评审者指南。
  • 解决所有 Sourcery 评论: 在 Pull Request 上评论 @sourcery-ai resolve 以解决所有 Sourcery 评论。如果您已经解决了所有评论并且不想再看到它们,这将非常有用。
  • 驳回所有 Sourcery 审查: 在 Pull Request 上评论 @sourcery-ai dismiss 以驳回所有现有的 Sourcery 审查。如果您想重新开始一个新的审查,这将特别有用 - 不要忘记评论 @sourcery-ai review 以触发新的审查!
  • 为 issue 生成行动计划: 在 issue 上评论 @sourcery-ai plan 以为其生成行动计划。

自定义您的体验

访问您的 仪表板 以:

  • 启用或禁用审查功能,例如 Sourcery 生成的 Pull Request 摘要、评审者指南等。
  • 更改审查语言。
  • 添加、删除或编辑自定义审查说明。
  • 调整其他审查设置。

获取帮助

```
Original review guide in English

Reviewer's Guide by Sourcery

This pull request updates the README with new deployment steps using uv and reorganizes the contribution guide into a separate file. It also enhances the README's layout and adds badges for project metrics.

Flow diagram for the new deployment steps

graph LR
    A[Clone the repository] --> B(Copy and edit the environment variables file)
    B --> C{Sync dependency environment using uv sync}
    C --> D{Run the bot using uv run app.py}
Loading

File-Level Changes

Change Details Files
Updated the README with new deployment steps using uv instead of pip.
  • Replaced pip sync with uv sync.
  • Replaced pip run with uv run.
README.md
Enhanced the README's layout and formatting for improved clarity and added various badges for project metrics.
  • Improved the overall layout and formatting of the README.
  • Added badges for license, Python version, code quality, and Ruff.
  • Added badges for uv, pre-commit, pyright, and ruff.
README.md
Moved the contribution guide to a separate CONTRIBUTING.md file.
  • Created a new CONTRIBUTING.md file.
  • Removed the contribution guide from the README.md.
README.md
CONTRIBUTING.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

嘿 @Qubbby - 我已经查看了你的更改 - 这里有一些反馈:

总体评论

  • 考虑在 README 中添加目录,以便更轻松地导航。
  • README 徽章看起来很棒,但考虑按逻辑对它们进行分组(例如,代码质量、项目状态)。
以下是我在审查期间查看的内容
  • 🟡 一般问题:发现 2 个问题
  • 🟢 安全性:一切看起来都不错
  • 🟢 测试:一切看起来都不错
  • 🟢 复杂性:一切看起来都不错
  • 🟢 文档:一切看起来都不错

Sourcery 对开源是免费的 - 如果你喜欢我们的评论,请考虑分享它们 ✨
帮助我更有用!请在每条评论上点击 👍 或 👎,我将使用反馈来改进你的评论。
Original comment in English

Hey @Qubbby - I've reviewed your changes - here's some feedback:

Overall Comments:

  • Consider adding a table of contents to the README for easier navigation.
  • The README badges look great, but consider grouping them logically (e.g., code quality, project status).
Here's what I looked at during the review
  • 🟡 General issues: 2 issues found
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟢 Complexity: all looks good
  • 🟢 Documentation: all looks good

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

<img src="https://codecov.io/gh/embyplus/embyBot/branch/master/graph/badge.svg" alt="codecov"/>
</a>
<br />
<a bref="https://github.com/astral-sh/ruff">
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

issue (typo): 错别字:"bref" 应该为 "href"

Suggested change
<a bref="https://github.com/astral-sh/ruff">
<a href="https://github.com/astral-sh/ruff">
Original comment in English

issue (typo): Typo: "bref" should be "href"

Suggested change
<a bref="https://github.com/astral-sh/ruff">
<a href="https://github.com/astral-sh/ruff">

Comment on lines +117 to +119
## 🎡 Activities

![Alt](https://repobeats.axiom.co/api/embed/079b23892e48f7b9e6be2f0cb2c66b2833eeffda.svg "Repobeats analytics image")
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion: 改进 "Activities" 部分

"Activities" 部分不清楚。请提供更多上下文并解释所指的活动。考虑将 Repobeats 分析链接移动到更合适的部分,例如 "Analytics" 或 "Code Quality" 中。

Original comment in English

suggestion: Improve "Activities" section

The "Activities" section is unclear. Provide more context and explain what activities are being referred to. Consider moving the Repobeats analytics link to a more appropriate section, such as "Analytics" or within "Code Quality".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant