Pull-request "linter"
Pull-request "linter"
我刚才看到一个工具可以让我为 GitHub pull-requests 定义规则，并且可以在 CI 期间强制执行。
规则可以是例如：
- 提交标题应符合格式
- 更改的文件数不能超过10
- 规范中不应有杂散的“:focus”
- 等等
我记不起这个工具的名字了。
thoughtbot 的 HoundCI 是一个非常流行的工具。它 SaaS-based 并且可以免费用于开源项目：https://houndci.com/
支持ruby和javascript。
我找到了我要找的工具：它叫做 Danger:
What is Danger?
Danger runs after your CI, automating your team's conventions
surrounding code review.
This provides another logical step in your process, through this
Danger can help lint your rote tasks in daily code review.
You can use Danger to codify your teams norms, leaving humans to think
about harder problems.
For example?
You can:
- Enforce CHANGELOGs Enforce links to Trello/JIRA in PR/MR bodies
- Enforce using descriptive labels Look out for common anti-patterns
- Highlight interesting build artifacts Give specific files extra focus
- Danger provides the glue to let you build out the rules specific to your team's culture, offering useful metadata and a comprehensive
plugin system to share common issues.
我刚才看到一个工具可以让我为 GitHub pull-requests 定义规则，并且可以在 CI 期间强制执行。
规则可以是例如：
- 提交标题应符合格式
- 更改的文件数不能超过10
- 规范中不应有杂散的“:focus”
- 等等
我记不起这个工具的名字了。
thoughtbot 的 HoundCI 是一个非常流行的工具。它 SaaS-based 并且可以免费用于开源项目：https://houndci.com/
支持ruby和javascript。
我找到了我要找的工具：它叫做 Danger:
What is Danger?
Danger runs after your CI, automating your team's conventions surrounding code review.
This provides another logical step in your process, through this Danger can help lint your rote tasks in daily code review.
You can use Danger to codify your teams norms, leaving humans to think about harder problems.
For example?
You can:
- Enforce CHANGELOGs Enforce links to Trello/JIRA in PR/MR bodies
- Enforce using descriptive labels Look out for common anti-patterns
- Highlight interesting build artifacts Give specific files extra focus
- Danger provides the glue to let you build out the rules specific to your team's culture, offering useful metadata and a comprehensive
plugin system to share common issues.