Adding upstream version 1.19.0.upstream/1.19.0

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>

6 files changed, 0 insertions, 128 deletions

diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
deleted file mode 100644
index bd939baba..000000000
--- a/.github/ISSUE_TEMPLATE.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-about: General issue template
-labels: "needs triage", "no changelog"
----
-
-<!---
-This is a generic issue template. We usually prefer contributors to use one
-of 3 other specific issue templates (bug report, feature request, question)
-to allow our automation classify those so you can get response faster.
-However if your issue doesn't fall into either one of those 3 categories
-use this generic template.
---->
-
-#### Summary
-
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
deleted file mode 100644
index d378d4512..000000000
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-name: Bug report
-about: Create a bug report to help us improve
-labels: bug, needs triage
----
-
-<!---
-When creating a bug report please:
-- Verify first that your issue is not already reported on GitHub
-- Test if the latest release and master branch are affected too.
-- Provide a clear and concise description of what the bug is in "Bug report 
-  summary" section.
-- Try to provide as much information about your environment (OS distribution,
-  running in container, etc.) as possible to allow us reproduce this bug faster.
-- Write which component is affected. We group our components the same way our
-  code is structured so basically:
-  component name = dir in top level directory of repository
-- Describe how you found this bug and how we can reproduce it. Preferable with
-  a minimal test-case scenario. You can paste gist.github.com links for larger
-  files
-- Provide a clear and concise description of what you expected to happen.
--->
-
-##### Bug report summary
-
-##### OS / Environment
-
-##### Netdata version (ouput of `netdata -V`)
-
-##### Component Name
-
-##### Steps To Reproduce
-
-##### Expected behavior
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
deleted file mode 100644
index 4d210259e..000000000
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-name: Feature request
-about: Suggest an idea for our project
-labels: feature request, needs triage
----
-
-<!---
-When creating a feature request please:
-- Verify first that your issue is not already reported on GitHub
-- Explain new feature briefly in "Feature idea summary" section
-- Provide a clear and concise description of what you expect to happen.
---->
-
-##### Feature idea summary
-
-##### Expected behavior
diff --git a/.github/ISSUE_TEMPLATE/question.md b/.github/ISSUE_TEMPLATE/question.md
deleted file mode 100644
index c5cd71e66..000000000
--- a/.github/ISSUE_TEMPLATE/question.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-name: Question
-about: You just want to ask a question? Go on.
-labels: question, no changelog
----
-
-<!---
-When asking a new question please:
-- Verify first that your question wasn't asked before on GitHub. 
-  HINT: Use label "question" when searching for such issues.
-- Briefly explain what is the problem you are having
-- Try to provide as much information about your environment (OS distribution,
-  running in container, etc.) as possible to allow us reproduce this bug faster.
-- Write which component is affected. We group our components the same way our
-  code is structured so basically:
-    component name = dir in top level directory of repository
-- Provide a clear and concise description of what you expected to happen.
--->
-
-##### Question summary
-
-##### OS / Environment
-
-##### Component Name
-
-##### Expected results
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
deleted file mode 100644
index b4932f9c5..000000000
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ /dev/null
@@ -1,19 +0,0 @@
-<!--
-Describe the change in summary section, including rationale and degin decisions.
-Include "Fixes #nnn" if you are fixing an existing issue.
-
-In "Component Name" section write which component is changed in this PR. This
-will help us review your PR quicker.
-
-If you have more information you want to add, write them in "Additional
-Information" section. This is usually used to help others understand your
-motivation behind this change. A step-by-step reproduction of the problem is
-helpful if there is no related issue.
--->
-
-##### Summary
-
-##### Component Name
-
-##### Additional Information
-
diff --git a/.github/stale.yml b/.github/stale.yml
deleted file mode 100644
index abf927a4f..000000000
--- a/.github/stale.yml
+++ /dev/null
@@ -1,18 +0,0 @@
----
-only: issues
-limitPerRun: 30
-daysUntilStale: 30
-daysUntilClose: 7
-exemptLabels:
-  - bug
-  - help wanted
-  - feature request
-exemptProjects: true
-exemptMilestones: true
-staleLabel: stale
-markComment: >
-  This issue has been inactive for 30 days.
-  It will be closed in one week, unless it is updated.
-closeComment: >
-  This issue has been automatically closed due to extended period of inactivity.
-  Please reopen if it is still valid. Thank you for your contributions.