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

[PR #1728] [MERGED] keep name after schedule completion or recreation #3924

New Issue
Closed
opened 2026-02-28 20:48:54 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 20:48:54 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/1728
Author: @shaankhosla
Created: 9/23/2023
Status: ✅ Merged
Merged: 9/24/2023
Merged by: @MatissJanis

Base: master ← Head: schedule_update

📝 Commits (4)

📊 Changes

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

View changed files

📝 packages/loot-core/src/server/schedules/app.ts (+0 -9)
➕ upcoming-release-notes/1728.md (+6 -0)

📄 Description

Fixes #1726

Not sure if this implementation is the best way to approach this problem, looking forward to feedback on this

🔄 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/1728 **Author:** [@shaankhosla](https://github.com/shaankhosla) **Created:** 9/23/2023 **Status:** ✅ Merged **Merged:** 9/24/2023 **Merged by:** [@MatissJanis](https://github.com/MatissJanis) **Base:** `master` ← **Head:** `schedule_update` --- ### 📝 Commits (4) - [`299d1b2`](https://github.com/actualbudget/actual/commit/299d1b2ae5ecdb1f024d20e8f89d496a6d48e0b3) keep name after schedule completion or recreation - [`80c36bd`](https://github.com/actualbudget/actual/commit/80c36bd1e4ac4a610421df87028561d2c1c15634) release notes - [`95c84e1`](https://github.com/actualbudget/actual/commit/95c84e11b85f31b6713a88bb01c21507e692ae26) linting - [`b548b75`](https://github.com/actualbudget/actual/commit/b548b75bc2d7e6cd354f86d1e823bb144ec4eb17) remove if statement ### 📊 Changes **2 files changed** (+6 additions, -9 deletions) <details> <summary>View changed files</summary> 📝 `packages/loot-core/src/server/schedules/app.ts` (+0 -9) ➕ `upcoming-release-notes/1728.md` (+6 -0) </details> ### 📄 Description Fixes #1726 Not sure if this implementation is the best way to approach this problem, looking forward to feedback on this --- <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 20:48:54 -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#3924
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?