mirror of
https://github.com/restic/restic.git
synced 2026-11-21 21:12:42 +00:00
* Small typos and clarification in contributing guide * cross-link contributing guide and issue/pr template * drop GOPATH mention * don't include merge commits in PRs * make high review delays explicit * explicitly ask for link to current PR in changelog template * clarify docs changes * use bug template as authoritative place' * consolidate development information in 090_participating Also move issue / PR creation relevant information into contributing.md. * clarify meaning of assigning to a pull request * link to minimum go version * minor typos * golanci-lint is always applied in full * add micro summary * more typo fixes * always run golangci-lint * Simplify issue/pr template * Fix IRC webchat link * Move security policy to SECURITY.md * address review comments
84 lines
2.3 KiB
Markdown
84 lines
2.3 KiB
Markdown
---
|
||
name: Bug report
|
||
about: Report a problem with restic to help us resolve it and improve
|
||
---
|
||
|
||
<!--
|
||
|
||
Welcome! - We kindly ask that you:
|
||
|
||
1. Fill out the issue template below - not doing so needs a good reason.
|
||
2. Use the forum if you have a question rather than a bug or feature request.
|
||
|
||
The forum is at https://forum.restic.net and is a better place for questions
|
||
about restic or general suggestions and topics, e.g. usage or documentation
|
||
questions! This issue tracker is mainly for tracking bugs and feature requests
|
||
directly relating to the development of the software itself.
|
||
|
||
Thanks for understanding, and for contributing to the project!
|
||
|
||
-->
|
||
|
||
|
||
Output of `restic version`
|
||
--------------------------
|
||
|
||
|
||
|
||
What backend/service did you use to store the repository?
|
||
---------------------------------------------------------
|
||
|
||
|
||
|
||
Problem description / Steps to reproduce
|
||
----------------------------------------
|
||
|
||
<!--
|
||
This section should include at least:
|
||
|
||
* A description of the problem you are having with restic.
|
||
|
||
* 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 often provides a clue.
|
||
|
||
* Clear and concise steps describing how to reproduce the behavior (if possible).
|
||
|
||
See https://github.com/restic/restic/blob/master/CONTRIBUTING.md#reporting-bugs
|
||
for ways to collect debug information if necessary.
|
||
-->
|
||
|
||
|
||
Expected behavior
|
||
-----------------
|
||
|
||
<!--
|
||
Describe what you'd like restic to do differently.
|
||
-->
|
||
|
||
Actual behavior
|
||
---------------
|
||
|
||
<!--
|
||
In this section, please try to concentrate on observations, so only describe
|
||
what you observed directly.
|
||
-->
|
||
|
||
Do you have any idea what may have caused this?
|
||
-----------------------------------------------
|
||
|
||
<!--
|
||
Did something noteworthy happen on your system, Internet connection, backend services, etc?
|
||
-->
|
||
|
||
|
||
Did restic help you today? Did it make you happy in any way?
|
||
------------------------------------------------------------
|
||
|
||
<!--
|
||
Answering this question is not required, but if you have anything positive to share, please do so here!
|
||
Sometimes we get tired of reading bug reports all day and a little positive end note does wonders.
|
||
Idea by Joey Hess, https://joeyh.name/blog/entry/two_holiday_stories/
|
||
-->
|