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

[GH-ISSUE #510] [Feature] Customizable backup naming template #7122

New Issue
Closed
opened 2026-04-10 16:48:03 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-10 16:48:03 -05:00
Owner
Copy Link

Originally created by @rich-howell on GitHub (Jan 22, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/510

Discussed in https://github.com/actualbudget/actual/discussions/261

Originally posted by rich-howell October 3, 2022
Ability to select or create a custom backup naming template.

When you export your data from actual, a template to enable custom naming and versioning if the backup is taken more than once per day E.G. yyyy-mm-dd-1.zip, yyyy-mm-dd-2.zip

Originally created by @rich-howell on GitHub (Jan 22, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/510 ### Discussed in https://github.com/actualbudget/actual/discussions/261 <div type='discussions-op-text'> <sup>Originally posted by **rich-howell** October 3, 2022</sup> Ability to select or create a custom backup naming template. When you export your data from actual, a template to enable custom naming and versioning if the backup is taken more than once per day E.G. yyyy-mm-dd-1.zip, yyyy-mm-dd-2.zip</div>
GiteaMirror added the feature label 2026-04-10 16:48:03 -05:00
GiteaMirror commented 2026-04-10 16:48:05 -05:00
Author
Owner
Copy Link

@rich-howell commented on GitHub (Jan 27, 2023):

I have submitted a PR that solves this #580

<!-- gh-comment-id:1407098603 --> @rich-howell commented on GitHub (Jan 27, 2023): I have submitted a PR that solves this #580
GiteaMirror commented 2026-04-10 16:48:06 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jan 27, 2023):

I have submitted a PR that solves this #580

IMO your PR is a step in the right direction, but not fully what the feature request was about.

How I read the feature request: the person wants to have a new field where you select the export format. And then depending on your selection - you either get yyyyMMdd, MM-dd-yyyy or some other format.

But your PR is still a step in the right direction and I think it's worth releasing it. :)

<!-- gh-comment-id:1407100340 --> @MatissJanis commented on GitHub (Jan 27, 2023): > I have submitted a PR that solves this #580 IMO your PR is a step in the right direction, but not fully what the feature request was about. How I read the feature request: the person wants to have a new field where you select the export format. And then depending on your selection - you either get `yyyyMMdd`, `MM-dd-yyyy` or some other format. But your PR is still a step in the right direction and I think it's worth releasing it. :)
GiteaMirror commented 2026-04-10 16:48:06 -05:00
Author
Owner
Copy Link

@rich-howell commented on GitHub (Jan 27, 2023):

It was actually my idea to begin with, I changed my mind and thought just adding the date would be good enough.

<!-- gh-comment-id:1407102147 --> @rich-howell commented on GitHub (Jan 27, 2023): It was actually my idea to begin with, I changed my mind and thought just adding the date would be good enough.
GiteaMirror commented 2026-04-10 16:48:06 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jan 27, 2023):

Oh. haha, I did not notice that :)

Sorry for my assumption.

<!-- gh-comment-id:1407103391 --> @MatissJanis commented on GitHub (Jan 27, 2023): Oh. haha, I did not notice that :) Sorry for my assumption.
GiteaMirror commented 2026-04-10 16:48:07 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 1, 2023):

✨ Thanks for sharing your idea! ✨

This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

<!-- gh-comment-id:1530125519 --> @github-actions[bot] commented on GitHub (May 1, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍!
GiteaMirror commented 2026-04-10 16:48:08 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Dec 4, 2024):

Closing as this was added in #580

<!-- gh-comment-id:2518445273 --> @youngcw commented on GitHub (Dec 4, 2024): Closing as this was added in #580
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 feature
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#7122
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?