Issues vs pull requests as a source

ReleaseJet can drive release notes from either closed issues or merged pull requests. Pick the one that matches how your team already plans work.

source: issues (default)

source: issues

Release notes are built from closed issues with matching category labels. Works on both GitLab and GitHub.

Best when issues are the primary unit of planning — every feature, bug, and improvement has an issue, and PRs are just the implementation detail that closes it.

source: pull_requests

source: pull_requests

Release notes are built from merged pull requests with matching category labels. Only the PR's merge counts — closed-but-not-merged PRs are skipped.

GitHub only. GitLab's API lacks the equivalent listing endpoint, so source: pull_requests on a GitLab provider fails at runtime.

Best when PRs are where the conversation lives — teams that don't file issues per change and rely on the PR description as the source of truth.

Trade-offs

Labeling is the same

Whichever source you use, category labels drive the sections exactly the same way — see Categorizing issues. You only need to apply the label to the thing that drives the notes (the issue or the PR).

Next steps

• Full config walk-through: GitHub + issues.
• PR-driven variant: GitHub + pull requests.