1
0
Fork 0
mirror of https://github.com/restic/restic.git synced 2024-12-26 17:57:50 +00:00
restic/.github/ISSUE_TEMPLATE.md

56 lines
1.4 KiB
Markdown
Raw Normal View History

2017-05-14 19:37:45 +00:00
<!--
2017-08-11 19:36:10 +00:00
NOTE: Not filling out the issue template needs a good reason, otherwise it may
take a lot longer to find the problem! Please take the time to help us
debugging the problem by collecting information, even if it seems irrelevant to
you. Thanks!
2017-10-21 08:17:58 +00:00
If you have a question, the forum at https://discourse.restic.net is a better place.
Please do not create issues for usage or documentation questions! We're using
the GitHub issue tracker mainly for tracking bugs and feature requests.
2017-05-14 19:37:45 +00:00
-->
2016-02-20 23:35:58 +00:00
## Output of `restic version`
2017-08-11 19:36:10 +00:00
## How did you run restic exactly?
<!--
2017-10-07 10:16:46 +00:00
This section should include at least:
* The complete command line and any environment variables you used to
configure restic's backend access. Make sure to replace sensitive values!
* The output of the commands, what restic prints gives may give us much
information to diagnose the problem!
2017-08-11 19:36:10 +00:00
-->
2017-11-25 10:43:44 +00:00
## What backend/server/service did you use to store the repository?
2016-02-20 23:35:58 +00:00
## Expected behavior
2017-10-07 10:16:46 +00:00
<!--
Describe what you'd like restic to do differently.
-->
2016-02-20 23:35:58 +00:00
## Actual behavior
2017-10-07 10:16:46 +00:00
<!--
In this section, please try to concentrate on observations, so only describe
what you observed directly.
-->
2016-02-20 23:35:58 +00:00
## Steps to reproduce the behavior
2017-10-07 10:16:46 +00:00
<!--
The more time you spend describing an easy way to reproduce the behavior (if
this is possible), the easier it is for the project developers to fix it!
-->
2016-02-20 23:35:58 +00:00
## Do you have any idea what may have caused this?
2017-08-11 19:36:10 +00:00
## Do you have an idea how to solve the issue?