Contact support

When the documentation does not have your answer, write in. ForkLeaf is built and answered by one person, and the inbox is read.

Where to write

Email support@forkleaf.in for anything specific to your account, your repository, or something you would rather not post in public. A reply usually takes a day or two, and it can land in your spam or junk folder, so look there before writing again. For bugs and feature requests that other people would hit too, GitHub Issues is better: it is searchable, and the fix is visible when it lands.

Security findings go through the security policy rather than the public tracker, so a flaw is fixed before it is advertised.

What to include

None of this is required, 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, including whatever is behind its “Details” or “Why” link.
• Your browser and operating system, and the note’s path if it is about one note.

Never send a GitHub token, a password, or a screenshot containing one. Nothing about a support request needs one.

While you wait

Your notes are Markdown files in a repository you own, in ordinary git history. Whatever is wrong with the app, you can clone that repository and keep working in any editor that reads text — nothing you are waiting on a reply for is holding your writing. The support page lists what to try first.