feat: add config-driven check-pr validation - #1706

@cchanche this is currently only a github action but I wonder if we should introduce it in CLI or support the different forge adapters.

So something like this:

  @release-drafter/core
  └── configuration, category primitives, normalized PR types

  @release-drafter/check-pr-title
  ├── title-validation policy
  ├── PullRequestReader port
  └── forge-neutral validation orchestration

  Forge adapters
  └── implement single PR/MR retrieval

  @release-drafter/gh-actions
  └── current GitHub event → validator

  @release-drafter/cli
  └── selected forge and PRs → validator

Yeah this sounds good to me.

selected forge and PRs → validator

current GitHub event → validator

Would validator be something like

import {PRTitleValidator} from @release-drafter/check-pr-title

...

const isValid = PRTitleValidator.validate(title)

... ?

Also, I like to think about changes in a more generic way (instead of simple PRs). Maybe this could be a higher level validator for any type of change. We'd omit a body and a footer for PR titles, and include them (sometimes) for commits. On top of doing the PR categorization stuff, we would prepare for whenever we want to implement commits into what we consider as possible changes.

Well ya thinking about it we could prepare it for semantic commit and semantic pr title support 👍

but then about the gh-action side of things, it would only make sense for the PR-titles I guess. So maybe two pacakges then ? One for the actual action @release-drafter/check-pr-title, and one for the lib @release-drafter/change-validator ? Or maybe @release-drafter/change-validator's content should simply be in @release-drafter/core

I think change-validator could live in core cause cli, gh-actions/check-pr-title and forge adapters may need pr fetching title support

Updated the stack around the design discussed here:

• the validation policy now lives in @release-drafter/core; there is no separate validator package
• the Action is now check-pr, not check-pr-title
• validation projects the configured categories to title (conventional) and label predicates only
• paths are deliberately ignored because Autolabeler owns path-based label assignment
• the CLI now exposes release-drafter check-pr <repository> <number> and uses the same core policy
• feat(adapters): add Gitea and Forgejo REST adapters #1707 and feat(adapters): add GitLab REST adapter #1708 add single-PR or MR readers for Gitea, Forgejo, and GitLab, while feat(facade): wire multiforge adapters #1709 wires those readers into the CLI

The Action uses the GitHub event payload directly, so it remains small and needs no forge request or separate package.