Get help

Alcuin’s questions, bugs and release notes all live in its repository on GitHub. Pick the place that fits what you have.

You have	Go to
A question	Discussions
A bug	Issues, then Bug
A security issue	The security policy
A new version	Releases

Before you ask, search these docs: the error codes and connection errors pages answer most messages by their exact text.

Ask a question

Ask in Discussions: how to do something, whether Alcuin can do something yet, or an idea. Issues are for bugs and accepted features.

Report a bug

1. Save a diagnostics bundle, and read it. It holds versions, the app’s small settings file, the names of any crash dumps and the last lines of Alcuin’s log, with credentials redacted.
2. Open Alcuin’s issues and choose Bug.
3. Fill in the Alcuin version (the bundle’s first line has it), your operating system, your Postgres version or provider, whether you connect directly or through an SSH tunnel, and whether a connection pooler is in between.
4. Under Steps to reproduce, write what you clicked or ran, in which view, and the exact message, if there was one. Copy details on a connection error, or Copy error in a query tab, copies the code and the message ready to paste.
5. Attach the bundle: drag the .txt file into the Diagnostics bundle or error text box, or paste the parts that matter.

An issue is public. A maintainer reads it and may ask for more, such as the steps on a fresh connection or a crash dump.

Report a security issue

Never put a security problem in an issue or a discussion. Report it privately, as the security policy says: Report a vulnerability, on the Security tab of Alcuin’s repository.

Release notes

Each version’s notes are on its page under Releases, and every change is in CHANGELOG.md. Updates says how Alcuin installs a new version.