Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

⭐ [Documentation] - Improve bank sync instructions/FAQs #490

Closed
matt-fidd opened this issue Nov 20, 2024 · 1 comment
Closed

⭐ [Documentation] - Improve bank sync instructions/FAQs #490

matt-fidd opened this issue Nov 20, 2024 · 1 comment
Assignees
Labels
Close at documentation merge When the corresponding documentation PR has been merged, the issue may also be closed documentation Improvements or additions to documentation enhancement New feature or request high priority This needs to be amended as soon as possible to prevent any misunderstandings PR under review A PR exists and is under review.

Comments

@matt-fidd
Copy link
Contributor

Description

At the moment, some common advice is hidden in the FAQ section at the bottom of the GoCardless page. Now that SimpleFIN is released first party the universal advice like "set a starting balance to avoid lots of historical data" should be moved to the parent page.

Documentation URL

https://actualbudget.org/docs/advanced/bank-sync

@matt-fidd matt-fidd added documentation Improvements or additions to documentation enhancement New feature or request labels Nov 20, 2024
@RubenOlsen RubenOlsen added the high priority This needs to be amended as soon as possible to prevent any misunderstandings label Jan 5, 2025
@RubenOlsen RubenOlsen self-assigned this Jan 6, 2025
RubenOlsen added a commit to RubenOlsen/ActualBudgetDocs that referenced this issue Jan 6, 2025
- Moved relevant information from gocardless.md to bank-syn.md and rewrote this to be general.
- Fixed header level from 3 to 2 in gocardless.md and simplefin.md.
@RubenOlsen RubenOlsen added the PR under review A PR exists and is under review. label Jan 6, 2025
@RubenOlsen RubenOlsen added the Close at documentation merge When the corresponding documentation PR has been merged, the issue may also be closed label Jan 6, 2025
@matt-fidd
Copy link
Contributor Author

@RubenOlsen FYI if you include the words "Fixes {issue number}" in your pull request description the issue will automatically close when the PR is closed.

Like:
Fixes #490

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Close at documentation merge When the corresponding documentation PR has been merged, the issue may also be closed documentation Improvements or additions to documentation enhancement New feature or request high priority This needs to be amended as soon as possible to prevent any misunderstandings PR under review A PR exists and is under review.
Projects
None yet
Development

No branches or pull requests

2 participants