Files
probot.github.io/_apps/semantic-pull-requests.md
Brandon Keepers 3bdc051995 Sync data
2018-12-30 21:56:19 +00:00

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
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 55 2018-12-10 18:30:41 UTC 132
electron
nuxt
monicahq
frappe
algolia
fossasia
electron-userland
greenkeeperio
tunnckoCore
renovatebot

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