Release notes & QA status: replace (#N) squash-subject regex with commits→PRs API
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Part of dotCMS/private-issues#673.
.github/scripts/gather-release-data/src/github.ts:147 and .github/scripts/release-qa-status/src/github.ts:139 extract PR numbers with the same (#N)$ regex. Under merge commits, merged PRs silently drop from release notes and the QA status section (release-qa-status warns at index.ts:272; gather-release-data is silent).
Fix: resolve PRs via GET /repos/{owner}/{repo}/commits/{sha}/pulls. Works under both merge strategies — safe to land now.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read .github/scripts/gather-release-data/src/github.ts:147 and .github/scripts/release-qa-status/src/github.ts:139, then compare their current PR-number extraction with the commits→pulls API described in the issue. Check release-qa-status/index.ts:272 for the existing warning behavior. Done means merged PRs are included in both release notes and QA status under merge commits as well as the current strategy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- release, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100