actions/pull-request-lint
2
0
Fork 0
Code Issues 1 Pull requests Projects Releases 5 Packages Wiki Activity Actions
Lints the title of a pull request
36 commits 2 branches 6 tags 143 KiB
Find a file
Renovate Bot c420551cdb
All checks were successful
Lint Pull Request / Lint PR Title (pull_request) Has been skipped
Details
chore: Configure Renovate (#4) 
Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

---
### Detected Package Files

 * `.gitea/workflows/pr.yml` (github-actions)
 * `.gitea/workflows/release.yml` (github-actions)
 * `.gitea/workflows/test.yml` (github-actions)
 * `go.mod` (gomod)

### Configuration Summary

Based on the default config's presets, Renovate will:

  - Start dependency updates only once this onboarding PR is merged
  - Enable Renovate Dependency Dashboard creation.
  - Use semantic commit type `fix` for dependencies and `chore` for all others if semantic commits are in use.
  - Ignore `node_modules`, `bower_components`, `vendor` and various test/tests (except for nuget) directories.
  - Group known monorepo packages together.
  - Use curated list of recommended non-monorepo package groupings.
  - Apply crowd-sourced package replacement rules.
  - Apply crowd-sourced workarounds for known problems with packages.
  - Preserve (but continue to upgrade) any existing SemVer ranges.
  - Enable Renovate Dependency Dashboard creation.
  - Rebase existing PRs any time the base branch has been updated.
  - Use semantic prefixes for commit messages and PR titles.
  - Raise PR when vulnerability alerts are detected with label `'security'`.
  - Group all `minor` and `patch` updates together.
  - Keep existing branches updated even when not scheduled.
  - Show all Merge Confidence badges for pull requests.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to `renovate.json` in this branch. Renovate will update the Pull Request description the next time it runs.

---

### What to Expect

With your current configuration, Renovate will create 2 Pull Requests:

<details>
<summary>chore(deps): update dependency go to 1.24</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/all-minor-patch`
  - Merge into: `main`
  - Upgrade [go](https://github.com/actions/go-versions) to `1.24`

</details>

<details>
<summary>chore(deps): update actions/setup-go action to v5</summary>

  - Schedule: ["at any time"]
  - Branch name: `renovate/actions-setup-go-5.x`
  - Merge into: `main`
  - Upgrade [actions/setup-go](https://github.com/actions/setup-go) to `v5`

</details>

---

❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section.
If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions).

---

This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).

<!--renovate-config-hash:0a0b8841b14278c0c061ba4db2615c8f351f5dda327a6ee5707d6e1ee5980f1c-->

Co-authored-by: Jan K9f <jan@kjan.email>
Reviewed-on: #4
Co-authored-by: Renovate Bot <renovate@kjan.de>
Co-committed-by: Renovate Bot <renovate@kjan.de>
2025-04-09 16:44:40 +00:00
.gitea/workflows refactor: some polishing 2025-04-09 18:29:31 +02:00
docs chore(release): [skip ci] 2025-04-09 16:32:02 +00:00
internal/validation refactor(validation): simplify regex and error messages 2025-04-09 18:37:58 +02:00
.gitignore Initial commit 2025-04-09 14:43:54 +00:00
action.yml refactor: some polishing 2025-04-09 18:29:31 +02:00
go.mod refactor: clean up unused dependencies and functions 2025-04-09 18:19:21 +02:00
go.sum refactor: clean up unused dependencies and functions 2025-04-09 18:19:21 +02:00
LICENSE Initial commit 2025-04-09 14:43:54 +00:00
main.go fix(main): improve error message for invalid PR title 2025-04-09 18:20:59 +02:00
README.md docs: update README with usage and validation rules (#7) 2025-04-09 16:43:32 +00:00
release.config.cjs feat(ci): add release workflow and configuration files (#1) 2025-04-09 14:52:48 +00:00
renovate.json chore: Configure Renovate (#4) 2025-04-09 16:44:40 +00:00

README.md

pull-request-lint

A GitHub/Gitea Action that lints pull request titles to ensure they follow the Conventional Commits format.

Usage

Add the following to your GitHub/Gitea workflow:

name: Pull Request Lint

on:
  pull_request:
    types: [opened, edited, reopened, synchronize]

jobs:
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Install go
        uses: actions/setup-go@v5
        with:
          go-version: 1.24.2
      - uses: https://git.kjan.de/actions/pull-request-lint@release

Validation Rules

The action enforces the following Conventional Commits rules for PR titles:

  • Format must be: type(scope)!: description (scope and breaking change marker ! are optional)
  • Type and scope must be lowercase
  • Description must start with lowercase
  • Breaking change indicator and footer are mutually exclusive
  • Body must be separated from description by a blank line
  • Footer tokens must use hyphens instead of spaces (except for "BREAKING CHANGE")

License

See LICENSE file for details.