github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[PR #4231] [CLOSED] Automatically close feature requests as "not planned" instead of "completed" #47094

New Issue
Closed
opened 2026-04-26 09:06:33 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-26 09:06:33 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/4231
Author: @e13h
Created: 1/23/2025
Status: ❌ Closed

Base: master ← Head: patch-1

📝 Commits (2)

  • dbc36bb Update issues-close-feature-requests.yml
  • 9b587fe Add release notes

📊 Changes

2 files changed (+7 additions, -1 deletions)

View changed files

📝 .github/workflows/issues-close-feature-requests.yml (+1 -1)
➕ upcoming-release-notes/4231.md (+6 -0)

📄 Description

I understand that the project uses lodash issue management and immediately closes feature requests. It's a little odd though that the GitHub issues are closed as "completed" by the bot when they pretty clearly are not complete. Since GitHub supports closing an issue as "not planned", can we do that instead?

🔄 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/4231 **Author:** [@e13h](https://github.com/e13h) **Created:** 1/23/2025 **Status:** ❌ Closed **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (2) - [`dbc36bb`](https://github.com/actualbudget/actual/commit/dbc36bb500bd042a9121467718260107c5421fba) Update issues-close-feature-requests.yml - [`9b587fe`](https://github.com/actualbudget/actual/commit/9b587fef78a7cee1f6e9bc68774060df875ce50a) Add release notes ### 📊 Changes **2 files changed** (+7 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/issues-close-feature-requests.yml` (+1 -1) ➕ `upcoming-release-notes/4231.md` (+6 -0) </details> ### 📄 Description I understand that the project uses lodash issue management and immediately closes feature requests. It's a little odd though that the GitHub issues are closed as "completed" by the bot when they pretty clearly are not complete. Since GitHub supports closing an issue as "not planned", can we do that instead? <!-- Thank you for submitting a pull request! Make sure to follow the instructions to write release notes for your PR — it should only take a minute or two: https://github.com/actualbudget/docs#writing-good-release-notes --> --- <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-04-26 09:06:33 -05: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#47094
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?