mirror of
https://github.com/ysoftdevs/terraform-aws-eks.git
synced 2026-03-28 04:11:07 +01:00
chore: Added action to validate PR title (#1715)
This commit is contained in:
30
.github/semantic.yml
vendored
30
.github/semantic.yml
vendored
@@ -1,30 +0,0 @@
|
|||||||
# Always validate the PR title, and ignore the commits
|
|
||||||
titleOnly: true
|
|
||||||
|
|
||||||
# Always validate all commits, and ignore the PR title
|
|
||||||
commitsOnly: false
|
|
||||||
|
|
||||||
# Always validate the PR title AND all the commits
|
|
||||||
titleAndCommits: false
|
|
||||||
|
|
||||||
# Require at least one commit to be valid
|
|
||||||
# this is only relevant when using commitsOnly: true or titleAndCommits: true,
|
|
||||||
# which validate all commits by default
|
|
||||||
anyCommit: false
|
|
||||||
|
|
||||||
# By default types specified in commitizen/conventional-commit-types is used.
|
|
||||||
# See: https://github.com/commitizen/conventional-commit-types/blob/v2.3.0/index.json
|
|
||||||
# You can override the valid types
|
|
||||||
types:
|
|
||||||
- feat
|
|
||||||
- fix
|
|
||||||
- improvement
|
|
||||||
- docs
|
|
||||||
- refactor
|
|
||||||
- test
|
|
||||||
- ci
|
|
||||||
- chore
|
|
||||||
|
|
||||||
# Allow use of Merge commits (eg on github: "Merge branch 'master' into feature/ride-unicorns")
|
|
||||||
# this is only relevant when using commitsOnly: true (or titleAndCommits: true)
|
|
||||||
allowMergeCommits: false
|
|
||||||
53
.github/workflows/pr-title.yml
vendored
Normal file
53
.github/workflows/pr-title.yml
vendored
Normal file
@@ -0,0 +1,53 @@
|
|||||||
|
name: "Validate PR title"
|
||||||
|
|
||||||
|
on:
|
||||||
|
pull_request_target:
|
||||||
|
types:
|
||||||
|
- opened
|
||||||
|
- edited
|
||||||
|
- synchronize
|
||||||
|
|
||||||
|
jobs:
|
||||||
|
main:
|
||||||
|
name: Validate PR title
|
||||||
|
runs-on: ubuntu-latest
|
||||||
|
steps:
|
||||||
|
# Please look up the latest version from
|
||||||
|
# https://github.com/amannn/action-semantic-pull-request/releases
|
||||||
|
- uses: amannn/action-semantic-pull-request@v3.4.6
|
||||||
|
env:
|
||||||
|
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||||
|
with:
|
||||||
|
# Configure which types are allowed.
|
||||||
|
# Default: https://github.com/commitizen/conventional-commit-types
|
||||||
|
types: |
|
||||||
|
fix
|
||||||
|
feat
|
||||||
|
docs
|
||||||
|
ci
|
||||||
|
chore
|
||||||
|
BREAKING CHANGE
|
||||||
|
# Configure that a scope must always be provided.
|
||||||
|
requireScope: false
|
||||||
|
# Configure additional validation for the subject based on a regex.
|
||||||
|
# This example ensures the subject starts with an uppercase character.
|
||||||
|
subjectPattern: ^[A-Z].+$
|
||||||
|
# If `subjectPattern` is configured, you can use this property to override
|
||||||
|
# the default error message that is shown when the pattern doesn't match.
|
||||||
|
# The variables `subject` and `title` can be used within the message.
|
||||||
|
subjectPatternError: |
|
||||||
|
The subject "{subject}" found in the pull request title "{title}"
|
||||||
|
didn't match the configured pattern. Please ensure that the subject
|
||||||
|
starts with an uppercase character.
|
||||||
|
# For work-in-progress PRs you can typically use draft pull requests
|
||||||
|
# from Github. However, private repositories on the free plan don't have
|
||||||
|
# this option and therefore this action allows you to opt-in to using the
|
||||||
|
# special "[WIP]" prefix to indicate this state. This will avoid the
|
||||||
|
# validation of the PR title and the pull request checks remain pending.
|
||||||
|
# Note that a second check will be reported if this is enabled.
|
||||||
|
wip: true
|
||||||
|
# When using "Squash and merge" on a PR with only one commit, GitHub
|
||||||
|
# will suggest using that commit message instead of the PR title for the
|
||||||
|
# merge commit, and it's easy to commit this by mistake. Enable this option
|
||||||
|
# to also validate the commit message for one commit PRs.
|
||||||
|
validateSingleCommit: false
|
||||||
Reference in New Issue
Block a user