简体中文
EnglishHow can I contact the restic project or community?
Updated
Use the forum for usage or support questions, and GitHub Issues for bugs or feature suggestions. restic's own Contact section lists these as the two primary channels, and it explicitly asks that bug reports and feature requests be filed through the issue template you are shown when opening an issue.
Which channel should you use?
| Your situation | Where to go | What to expect |
|---|---|---|
| You have a usage or support question | The restic forum | A community space for questions and answers |
| You found a bug | GitHub issue | A tracked report; fill out the issue template |
| You have a feature suggestion | GitHub issue | Same as above — the site groups bugs and feature suggestions together |
| You want to contribute code or docs | Contribution guidelines | Separate from support contact |
The distinction matters because the project routes support traffic to the forum and defect/feature traffic to GitHub. Posting a support question as a GitHub issue, or a bug report in the forum, is likely to get redirected.
Filing a bug or feature request
The site gives one concrete instruction beyond "open an issue": fill out the issue template you are presented with. That template appears automatically when you start a new issue, so the practical steps are:
- Go to the restic GitHub project.
- Open a new issue.
- Complete the template fields rather than deleting them.
- Submit.
The expected result is a report the maintainers can act on without a round-trip asking for basics. The site does not describe what fields the template contains, so check the template itself when you open it.
Other ways to reach the project
The Contact section also points to the contribution guidelines and the design document for people who want to contribute or understand restic's internals — these are documentation, not support channels. The page excerpt ends mid-sentence after the GitHub issue guidance, so any additional contact methods (mailing lists, chat, etc.) are not confirmed by the available material. Treat the forum and GitHub as the two verified routes.
Before you post
- For support questions, the manual is the first stop: restic publishes a manual for the released version and one for the latest development version. Many usage questions are answered there.
- For bugs, note that restic follows Semantic Versioning, and the repository and its data structures are treated as the "Public API." If your issue involves restoring older backups, mentioning your restic version helps, since backward compatibility is guaranteed within a major version once 1.0.0 is released.
- For anything involving a specific backup or repository, include the restic version and the command you ran — the site does not require this, but it is the kind of detail a template typically asks for.