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 #6029] 📑 merge actualbudget/docs into main repo #6278

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

Original Pull Request: https://github.com/actualbudget/actual/pull/6029

State: closed
Merged: Yes

This is something we've talked about and considered for a while, but not come to a full conclusion on - at least, not that I can remember. I thought getting a PR together makes it easier for a yes/no vote, so, here it is!

I've taken the same approach as Mike did with the server merge and brought all of the history over. There will need to be a cleanup PR after this one to deduplicate config files, integrate github workflows and then when we're ready we can change netlify to point here for the website, but I've left that out of this PR to make the review easier.

(maintainers with edit access, feel free to add to the below)

Pros:

  • Easier to review docs PRs and see issues, won't be missed if the other repo is not checked
  • Keeps code and docs changes in the same PR
  • We can increase release automation even more, adding the blog posts when the PR is generated

Cons:

  • Lose the separation and less control over when public docs pages are updated
  • Possibility to clog up main repo issues with docs ones, although we can look at ways of managing those
**Original Pull Request:** https://github.com/actualbudget/actual/pull/6029 **State:** closed **Merged:** Yes --- This is something we've talked about and considered for a while, but not come to a full conclusion on - at least, not that I can remember. I thought getting a PR together makes it easier for a yes/no vote, so, here it is! I've taken the same approach as Mike did with the server merge and brought all of the history over. There will need to be a cleanup PR after this one to deduplicate config files, integrate github workflows and then when we're ready we can change netlify to point here for the website, but I've left that out of this PR to make the review easier. (maintainers with edit access, feel free to add to the below) Pros: - Easier to review docs PRs and see issues, won't be missed if the other repo is not checked - Keeps code and docs changes in the same PR - We can increase release automation even more, adding the blog posts when the PR is generated Cons: - Lose the separation and less control over when public docs pages are updated - Possibility to clog up main repo issues with docs ones, although we can look at ways of managing those
GiteaMirror added the pull-request label 2026-02-28 21:26:06 -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#6278
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?