summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLukas Fleischer <lfleischer@calcurse.org>2019-06-06 20:45:15 -0400
committerLukas Fleischer <lfleischer@calcurse.org>2019-06-06 20:57:48 -0400
commit16b346a1f485941bce108ae07d8a1abc3d4d852c (patch)
treefa43dbe5e947175961003c0f605ab16cc71be11a
parent987fa9d3e5db8549612db7a8f1c05f7e7a19d224 (diff)
downloadcalcurse-16b346a1f485941bce108ae07d8a1abc3d4d852c.tar.gz
calcurse-16b346a1f485941bce108ae07d8a1abc3d4d852c.zip
Add GitHub gimmicks
Add a bug report template and a sponsor button to the GitHub interface. Signed-off-by: Lukas Fleischer <lfleischer@calcurse.org>
-rw-r--r--.github/FUNDING.yml1
-rw-r--r--.github/ISSUE_TEMPLATE/bug_report.md18
2 files changed, 19 insertions, 0 deletions
diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml
new file mode 100644
index 0000000..81520d4
--- /dev/null
+++ b/.github/FUNDING.yml
@@ -0,0 +1 @@
+custom: https://calcurse.org/donate/
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 0000000..5c8a1b5
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,18 @@
+---
+name: Bug report
+about: Report a bug in calcurse or calcurse-caldav
+---
+
+_Please replace template text and remove irrelevant lines (including this one)._
+
+*Before filing a new bug report, make sure you use the search function to check whether the bug has already been reported.*
+
+**Version information.** Specify the calcurse version you are using. If you are not using the most recent release (or a newer development snapshot), please upgrade first. Make sure the bug still exists before reporting a bug. If you are running a development snapshot, please specify the commit you are using (i.e. the output of `git describe --dirty`). Make sure you are not using a version with custom changes.
+
+**Bug description.** Provide a clear and concise description of what the bug is.
+
+**Reproduce.** Please try to reproduce the bug before reporting. Describe steps to reproduce the behavior.
+
+**Expected Behavior.** A clear and concise description of what you expected to happen.
+
+**Screenshots.** If applicable, you can add screenshots to help explain your problem.