Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Update mergify configuration #1015

Merged
merged 2 commits into from
Aug 18, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions .mergify.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,4 +4,25 @@ pull_request_rules:
- base=master
actions:
merge:
strict: true
strict_method: rebase
method: squash
- name: ask to fix PR title
conditions:
- status-failure=check_title
- -closed
actions:
comment:
message: |
Title does not follow the guidelines of [Conventional Commits](https://www.conventionalcommits.org).
Please adjust title before merge and use one of following prefix:
- `build` - Changes that affect the build system or external dependencies (dependencies update)
- `ci` - Changes to our CI configuration files and scripts (basically directory `.github/workflows`)
- `docs` - Documentation only changes
- `feat` - A new feature
- `fix` - A bug fix
- `chore` - Changes which does not touch the code (ex. manual update of release notes). It will not generate release notes changes
- `refactor` - A code change that contains refactor
- `style` - Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
- `test` - Adding missing tests or correcting existing tests and also changes for our test app
- `perf` - A code change that improves performance (I do not think we will use it)