kylefang/probot.github.io
1
0
Fork 0
mirror of https://github.com/zhigang1992/probot.github.io.git synced 2026-01-12 22:49:53 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
dcef029dc27d6f31fef763bbd843890848eaef72
probot.github.io/_apps/semantic-pull-requests.md
Brandon Keepers 86f008a394 Sync data
2018-08-10 20:33:59 +00:00

2.2 KiB
Raw Blame History

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
https://user-images.githubusercontent.com/2289/42729629-110812b6-8793-11e8-8c35-188b0952fd66.png
https://user-images.githubusercontent.com/2289/42729632-11980b32-8793-11e8-9f8d-bf16c707f542.png
zeke
bkeepers
probot/semantic-pull-requests https://probot-semantic-pull-requests.herokuapp.com 12 2018-07-25 18:27:18 UTC 28
electron
algolia
greenkeeperio
renovatebot
stardust-ui
cozy
probot
crowdin-modules
seantrane
mike-north

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:

screen shot 2018-07-14 at 6 22 58 pm screen shot 2018-07-14 at 6 22 10 pm

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:

screen shot 2018-07-14 at 6 23 11 pm screen shot 2018-07-14 at 6 23 23 pm

Installation

👉 github.com/apps/semantic-pull-requests