Adding upstream version 3.5.1.

Signed-off-by: Daniel Baumann <daniel@debian.org>

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,41 @@
+---
+name: Bug report
+about: For behaviors which violate documentation or cause incorrect results
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!--
+This template is for bug reports! (If your issue doesn't fit this template, it's probably a feature request instead.)
+To fill out this template, simply replace these comments with your answers.
+Please do not skip questions; this will slow down the resolution process.
+-->
+
+## What version of the package or command are you using?
+<!-- A commit sha or tag is fine -->
+
+
+## What are you trying to do?
+<!-- Please describe clearly what you are trying to do thoroughly enough so that a reader with no context can repeat the same process. -->
+
+
+## What steps did you take?
+<!-- Explain exactly how we can reproduce this bug; attach sample archive files if relevant -->
+
+
+## What did you expect to happen, and what actually happened instead?
+<!-- Please make it clear what the bug actually is -->
+
+
+## How do you think this should be fixed?
+<!-- Being specific by linking to lines of code and even suggesting changes will yield fastest resolution -->
+
+
+## Please link to any related issues, pull requests, and/or discussion
+<!-- This will help add crucial context to your report -->
+
+
+## Bonus: What do you use archiver for, and do you find it useful?
+<!-- We'd like to know! -->

.github/ISSUE_TEMPLATE/generic-feature-request.md

@@ -0,0 +1,28 @@
+---
+name: Generic feature request
+about: Suggest an idea for this project
+title: ''
+labels: feature request
+assignees: ''
+
+---
+
+<!--
+This issue template is for feature requests! If you are reporting a bug instead, please switch templates.
+To fill this out, simply replace these comments with your answers.
+-->
+
+## What would you like to have changed?
+<!-- Describe the feature or enhancement you are requesting -->
+
+
+## Why is this feature a useful, necessary, and/or important addition to this project?
+<!-- Please justify why this change adds value to the project, considering the added maintenance burden and complexity the change introduces -->
+
+
+## What alternatives are there, or what are you doing in the meantime to work around the lack of this feature?
+<!-- We want to get an idea of what is being done in practice, or how other projects support your feature -->
+
+
+## Please link to any relevant issues, pull requests, or other discussions.
+<!-- This adds crucial context to your feature request and can speed things up -->

.github/ISSUE_TEMPLATE/new-format-request.md

@@ -0,0 +1,32 @@
+---
+name: New format request
+about: Request a new archival or compression format
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!--
+This template is specifically for adding support for a new archive or compression format to the library. Please, precisely one format per issue.
+To fill this out, replace these comments with your answers.
+-->
+
+## Introduce the format you are requesting.
+<!-- What is it called, what is it used for, etc? Some background information. -->
+
+
+## What do YOU use this format for?
+<!-- We want to know YOUR specific use cases; why do YOU need this format? -->
+
+
+## What is the format's conventional file extension(s)?
+<!-- Don't overthink this one, it's a simple question. -->
+
+
+## Please link to the format's formal or official specification(s).
+<!-- If there isn't a formal spec, link to the most official documentation for the format. Note that unstandardized formats are less likely to be added unless it is in high-enough demand. -->
+
+
+## Which Go libraries could be used to implement this format?
+<!-- This project itself does not actually implement low-level format reading and writing algorithms, so link to pure-Go libraries that do. Dependencies that use cgo or invoke external commands are not eligible for this project. -->