Remove unused .github directories

They were valid until the switch to the "monorepository" when everything
was merged into a single Git repository.

2 files changed, 0 insertions, 64 deletions

diff --git a/deps/rabbitmq_tracing/.github/ISSUE_TEMPLATE.md b/deps/rabbitmq_tracing/.github/ISSUE_TEMPLATE.md
deleted file mode 100644
index bce561261a..0000000000
--- a/deps/rabbitmq_tracing/.github/ISSUE_TEMPLATE.md
+++ /dev/null
@@ -1,21 +0,0 @@
-Thank you for using RabbitMQ.
-
-**STOP NOW AND READ THIS** BEFORE OPENING A NEW ISSUE ON GITHUB
-
-Unless you are CERTAIN you have found a reproducible problem in RabbitMQ or
-have a **specific, actionable** suggestion for our team, you must first ask
-your question or discuss your suspected issue on the mailing list:
-
-https://groups.google.com/forum/#!forum/rabbitmq-users
-
-Team RabbitMQ does not use GitHub issues for discussions, investigations, root
-cause analysis and so on.
-
-Please take the time to read the CONTRIBUTING.md document for instructions on
-how to effectively ask a question or report a suspected issue:
-
-https://github.com/rabbitmq/rabbitmq-server/blob/master/CONTRIBUTING.md#github-issues
-
-Following these rules **will save time** for both you and RabbitMQ's maintainers.
-
-Thank you.
diff --git a/deps/rabbitmq_tracing/.github/PULL_REQUEST_TEMPLATE.md b/deps/rabbitmq_tracing/.github/PULL_REQUEST_TEMPLATE.md
deleted file mode 100644
index 230febf8a2..0000000000
--- a/deps/rabbitmq_tracing/.github/PULL_REQUEST_TEMPLATE.md
+++ /dev/null
@@ -1,43 +0,0 @@
-## Proposed Changes
-
-Please describe the big picture of your changes here to communicate to the
-RabbitMQ team why we should accept this pull request. If it fixes a bug or
-resolves a feature request, be sure to link to that issue.
-
-A pull request that doesn't explain **why** the change was made has a much
-lower chance of being accepted.
-
-If English isn't your first language, don't worry about it and try to
-communicate the problem you are trying to solve to the best of your abilities.
-As long as we can understand the intent, it's all good.
-
-## Types of Changes
-
-What types of changes does your code introduce to this project?
-_Put an `x` in the boxes that apply_
-
-- [ ] Bug fix (non-breaking change which fixes issue #NNNN)
-- [ ] New feature (non-breaking change which adds functionality)
-- [ ] Breaking change (fix or feature that would cause an observable behavior change in existing systems)
-- [ ] Documentation improvements (corrections, new content, etc)
-- [ ] Cosmetic change (whitespace, formatting, etc)
-
-## Checklist
-
-_Put an `x` in the boxes that apply. You can also fill these out after creating
-the PR. If you're unsure about any of them, don't hesitate to ask on the
-mailing list. We're here to help! This is simply a reminder of what we are
-going to look for before merging your code._
-
-- [ ] I have read the `CONTRIBUTING.md` document
-- [ ] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
-- [ ] All tests pass locally with my changes
-- [ ] I have added tests that prove my fix is effective or that my feature works
-- [ ] I have added necessary documentation (if appropriate)
-- [ ] Any dependent changes have been merged and published in related repositories
-
-## Further Comments
-
-If this is a relatively large or complex change, kick off the discussion by
-explaining why you chose the solution you did and what alternatives you
-considered, etc.