Workflow to ensure Pull Request provides semantic versionning assets:
- "Squash and merge" Pull Request strategy provides a valid commit message. Check that the title follows the Conventional Commits specification. Mainly using action-semantic-pull-request, with some opinionated defaults.
name: "Pull Request - Semantic Lint"
on:
pull_request_target:
types:
- opened
- edited
- synchronize
permissions:
contents: write
pull-requests: write
jobs:
main:
uses: hoverkraft-tech/ci-github-common/.github/workflows/semantic-pull-request.yml@0.23.1
secrets:
# Token for the repository.
# Default GITHUB_TOKEN
github-token: ""| Secret | Description | Required |
|---|---|---|
github-token |
Token for the repository. | false |
| Input | Description | Default | Type | Required |
|---|---|---|---|---|
runs-on |
JSON array of runner(s) to use. See https://docs.github.com/en/actions/using-jobs/choosing-the-runner-for-a-job. | ["ubuntu-latest"] |
string |
false |