Skip to content

Conversation

@MatKuhr
Copy link
Member

@MatKuhr MatKuhr commented Jan 13, 2025

Examples which are allowed:

  • chore: [DevOps] PR Title Linter
  • chore: [DevOps] pr title linter
  • chore: PR Title Linter

Examples which are not allowed:

  • PR Title Linter
  • [DevOps] PR Title Linter
  • chore: [Foo] PR Title Linter

Tested on my fork

@MatKuhr MatKuhr added the please-review Request to review a pull-request label Jan 13, 2025
Comment on lines +3 to +8
on:
pull_request_target:
types:
- opened
- edited
- synchronize
Copy link
Contributor

@newtork newtork Jan 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(Comment/Opinion)

I didn't expect this syntax to be mandatory.

  • It may discourage future, external contributors.
  • It may break current and future automated PRs.

It's not possible to make this more like a warning/notification right?

Copy link
Member Author

@MatKuhr MatKuhr Jan 13, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

more like a warning

No, at least not per the docs. I checked that it works with Dependabot, but Release PRs would currently fail. Updated the script ✅. For external contributors it should be fine, because it is easy to fix and only occurs after a PR is already raised, i.e. when most of the work is already done.

@MatKuhr MatKuhr enabled auto-merge (squash) January 13, 2025 09:29
@MatKuhr MatKuhr merged commit 44700cf into main Jan 16, 2025
5 checks passed
@MatKuhr MatKuhr deleted the chore/pr-title-linter branch January 16, 2025 13:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

please-review Request to review a pull-request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants