mirror of
https://github.com/zhigang1992/probot.github.io.git
synced 2026-01-12 22:49:53 +08:00
2.2 KiB
2.2 KiB
title, description, slug, screenshots, authors, repository, host, stars, updated, installations, organizations
| title | description | slug | screenshots | authors | repository | host | stars | updated | installations | organizations | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Semantic Pull Requests | Status check that ensures your pull requests follow the Conventional Commits spec | semantic-pull-requests |
|
|
probot/semantic-pull-requests | https://probot-semantic-pull-requests.herokuapp.com | 59 | 2019-01-08 15:17:38 UTC | 146 |
|
GitHub status check that ensures your pull requests follow the Conventional Commits spec
Using semantic-release and conventional commit messages? Install this app on your repos to ensure your pull requests are semantic before you merge them.
How it works
Take this PR for example. None of the commit messages are semantic, nor is the PR title, so the status remains yellow:
Edit the PR title by adding a semantic prefix like fix: or feat: or any other
conventional commit type. Now use Squash and Merge to squash the branch onto master and write a standardized commit message while doing so:
