Getting help

ForkLeaf is built and answered by one person. Write in about anything — a bug, a note that will not sync, a question about your data, or something you wish it did.

Email

praneeth2006.dev@gmail.com — the fastest route for anything specific to your account, your repository, or something you would rather not post in public. It is the same address the Privacy Policy gives for data requests.

One person reads it, so a reply usually takes a day or two rather than an hour. There is no paid tier that gets answered sooner.

What to include

None of this is required — a one-line description of what went wrong is a perfectly good email. But a report with these in it can usually be answered rather than asked about:

• What you were doing, and what happened instead.
• Whether the repository is connected to GitHub or the notes are local to that browser.
• The exact text of any error the app showed, including anything under a “Details” or “Why” link — those messages carry the reason the plain sentence leaves out.
• Your browser and operating system.
• The note’s path if it is about one note — Fieldwork/soil.md rather than “the soil one”.

Please do not send a GitHub token, a password, or a screenshot with one in it. Nothing about a support request needs one, and an address that asks for credentials is one you should be suspicious of.

Things worth trying first

These resolve most of what gets reported, and take less time than an email:

1. Read Troubleshooting — it lists the errors people actually hit and what each one means.
2. If changes are not reaching GitHub, open the sync status in the editor’s status bar. A failed push says why it failed and what to do about it, and a push that was refused for being too large names the file.
3. If you have been signed out, sign in again from the sign-in page. Local notes are untouched by signing out.
4. If a note looks wrong, its history is on github.com — every save is a commit, and the previous version is one click away.

Bugs and feature requests in public

GitHub Issues is the better place for anything other people would hit too. It is searchable, other users can add to it, and the fix is visible when it lands. ForkLeaf is open source under Apache-2.0, so a pull request is welcome as well.

Security

Please do not open a public issue for a vulnerability. The security policy explains how to report one privately so it can be fixed before it is advertised. Email works too — say “security” in the subject and it will be read first.

What this costs

Nothing. ForkLeaf is free, all of it, with no tiers — see what it costs. Support is not a product being sold here, which is also why it is one person’s inbox rather than a helpdesk.