github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[PR #5134] [MERGED] fix: ensure correct PR number is used for release notes file #5775

New Issue
Closed
opened 2026-02-28 21:18:23 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 21:18:23 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/5134
Author: @OlivierKamers
Created: 6/10/2025
Status: ✅ Merged
Merged: 6/10/2025
Merged by: @matt-fidd

Base: master ← Head: oli/fix-release-notes-pr-number

📝 Commits (1)

  • 2894a26 fix: ensure correct PR number is used for release notes file

📊 Changes

2 files changed (+12 additions, -6 deletions)

View changed files

📝 bin/release-note-generator.ts (+6 -6)
➕ upcoming-release-notes/5134.md (+6 -0)

📄 Description

I usually create a draft PR before I generate the release notes and I found that the prompt value for PR number is not used for determining the file path, as it only uses the initial value. For me this didn't work because I'm not authenticated through the Github CLI so it will always use the value from getNextPrNumber, which is my draft PR number + 1. This change fixes it by using the inferred number as initial value for the command line prompt, and reading the actual value to be used for the file path.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/5134 **Author:** [@OlivierKamers](https://github.com/OlivierKamers) **Created:** 6/10/2025 **Status:** ✅ Merged **Merged:** 6/10/2025 **Merged by:** [@matt-fidd](https://github.com/matt-fidd) **Base:** `master` ← **Head:** `oli/fix-release-notes-pr-number` --- ### 📝 Commits (1) - [`2894a26`](https://github.com/actualbudget/actual/commit/2894a26c31c1412077547c1f0a994d044fd3c33f) fix: ensure correct PR number is used for release notes file ### 📊 Changes **2 files changed** (+12 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `bin/release-note-generator.ts` (+6 -6) ➕ `upcoming-release-notes/5134.md` (+6 -0) </details> ### 📄 Description I usually create a draft PR before I generate the release notes and I found that the prompt value for PR number is not used for determining the file path, as it only uses the initial value. For me this didn't work because I'm not authenticated through the Github CLI so it will always use the value from `getNextPrNumber`, which is my draft PR number + 1. This change fixes it by using the inferred number as initial value for the command line prompt, and reading the actual value to be used for the file path. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-02-28 21:18:23 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#5775
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?