Mzdyl / LiteLoaderQQNT_Install

针对 LiteLoaderQQNT 的安装脚本
BSD 3-Clause "New" or "Revised" License
1.43k stars 53 forks source link

有关action控制的更改 #164

Closed LY-Xiang closed 4 days ago

LY-Xiang commented 1 week ago

采用test与prerelease两个标签控制构建 更有可控性(

sourcery-ai[bot] commented 1 week ago

审核指南 by Sourcery

此 PR 通过将触发机制从基于提交消息更改为基于标签的控制,修改了 Windows 构建的 GitHub Actions 工作流。更改实现了一种更结构化的方法来使用 'test' 和 'prerelease' 标签管理构建和发布,并在执行后自动清理标签。

未生成图表,因为更改看起来简单,不需要视觉表示。

文件级更改

更改 详情 文件
将构建触发机制从提交消息更改为标签
  • 移除提交消息 'pre-release' 检查
  • 添加 'prerelease' 和 'test' 标签作为触发条件
  • 更新发布作业条件以检查 'prerelease' 标签
.github/workflows/windows.yml
添加自动标签清理功能
  • 在构建后添加 'test' 标签清理步骤
  • 在发布后添加 'prerelease' 标签清理步骤
  • 添加内容操作的写权限
.github/workflows/windows.yml
增强的检出配置
  • 添加显式的 ref 检出
  • 在检出期间启用标签获取
.github/workflows/windows.yml

提示和命令 #### 与 Sourcery 互动 - **触发新审核:** 在拉取请求中评论 `@sourcery-ai review`。 - **继续讨论:** 直接回复 Sourcery 的审核评论。 - **从审核评论生成 GitHub 问题:** 通过回复审核评论请求 Sourcery 创建问题。 - **生成拉取请求标题:** 在拉取请求标题中任意位置写 `@sourcery-ai` 以随时生成标题。 - **生成拉取请求摘要:** 在拉取请求正文中任意位置写 `@sourcery-ai summary` 以随时生成 PR 摘要。您也可以使用此命令指定摘要应插入的位置。 #### 自定义您的体验 访问您的[仪表板](https://app.sourcery.ai)以: - 启用或禁用审核功能,如 Sourcery 生成的拉取请求摘要、审核指南等。 - 更改审核语言。 - 添加、删除或编辑自定义审核说明。 - 调整其他审核设置。 #### 获取帮助 - [联系我们的支持团队](mailto:support@sourcery.ai)以获取问题或反馈。 - 访问我们的[文档](https://docs.sourcery.ai)以获取详细指南和信息。 - 通过关注我们在 [X/Twitter](https://x.com/SourceryAI)、[LinkedIn](https://www.linkedin.com/company/sourcery-ai/) 或 [GitHub](https://github.com/sourcery-ai) 上的 Sourcery 团队保持联系。
Original review guide in English ## Reviewer's Guide by Sourcery This PR modifies the GitHub Actions workflow for Windows builds by changing the trigger mechanism from commit message-based to tag-based control. The changes implement a more structured approach to managing builds and releases using 'test' and 'prerelease' tags, with automatic tag cleanup after execution. _No diagrams generated as the changes look simple and do not need a visual representation._ ### File-Level Changes | Change | Details | Files | | ------ | ------- | ----- | | Changed build trigger mechanism from commit message to tags |
  • Removed commit message 'pre-release' check
  • Added 'prerelease' and 'test' tags as trigger conditions
  • Updated release job condition to check for 'prerelease' tag
| `.github/workflows/windows.yml` | | Added automatic tag cleanup functionality |
  • Added cleanup step for 'test' tag after build
  • Added cleanup step for 'prerelease' tag after release
  • Added write permissions for content manipulation
| `.github/workflows/windows.yml` | | Enhanced checkout configuration |
  • Added explicit ref checkout
  • Enabled tag fetching during checkout
| `.github/workflows/windows.yml` | ---
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. - **Generate a pull request title:** Write `@sourcery-ai` anywhere in the pull request title to generate a 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. You can also use this command to specify where the summary should be inserted. #### Customizing Your Experience Access your [dashboard](https://app.sourcery.ai) 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 - [Contact our support team](mailto:support@sourcery.ai) for questions or feedback. - Visit our [documentation](https://docs.sourcery.ai) for detailed guides and information. - Keep in touch with the Sourcery team by following us on [X/Twitter](https://x.com/SourceryAI), [LinkedIn](https://www.linkedin.com/company/sourcery-ai/) or [GitHub](https://github.com/sourcery-ai).
Mzdyl commented 1 week ago

这个好像没啥必要吧(

README 中也已经写了测试版可以通过 Github Action 中获取 感觉光用个 pre-release 作为预发布差不多了?

LY-Xiang commented 4 days ago

用tag会灵活一点 毕竟预发布版本与单次提交没有强关联性

LY-Xiang commented 4 days ago

当然其实也不必要(

Mzdyl commented 4 days ago

感觉发布应该不成问题( 毕竟目前基本是每隔一段时间写一点,而不像那些大项目每天都活跃更新 维持一个简单的发布控制即可(

先关了吧,感觉大概率目前用不到

LY-Xiang commented 4 days ago

ok