Removing references to issues from the contributer and maintainer gui…

…des.

.github/CONTRIBUTING.md

@@ -7,6 +7,8 @@ well.
 There are many ways you can contribute! :heart:
 
 ### Bug Reports and Fixes :bug:
+- At this early stage of development we are not accepting bug reports or feature requests through GitHub. Yet.
+<!--
 -  If you find a bug, please search for it in the [Issues](https://github.com/slackapi/deno-slack-api/issues), and if it isn't already tracked,
    [create a new issue](https://github.com/slackapi/deno-slack-api/issues/new). Fill out the "Bug Report" section of the issue template. Even if an Issue is closed, feel free to comment and add details, it will still
    be reviewed.
@@ -30,6 +32,7 @@ There are many ways you can contribute! :heart:
 
 If you're new to our project and looking for some way to make your first contribution, look for
 Issues labelled `good first contribution`.
+-->
 
 ## Requirements
 
@@ -52,7 +55,7 @@ If the contribution doesn't meet the above criteria, you may fail our automated
 3.  :herb: Create a new branch and check it out.
 4.  :crystal_ball: Make your changes and commit them locally. Magic happens here!
 5.  :arrow_heading_up: Push your new branch to your fork. (e.g. `git push username fix-issue-16`).
-6.  :inbox_tray: Open a Pull Request on github.com from your new branch on your fork to `master` in this
+6.  :inbox_tray: Open a Pull Request on github.com from your new branch on your fork to `main` in this
     repository.
 
 ## Maintainers

.github/maintainers_guide.md

@@ -59,6 +59,7 @@ This project is versioned using [Semantic Versioning][semver].
 > `main` is where active development occurs.
 > Long running branches named feature branches are occasionally created for collaboration on a feature that has a large scope (because everyone cannot push commits to another person's open Pull Request)
 
+<!--
 ### Issue Management
 
 Labels are used to run issues through an organized workflow. Here are the basic definitions:
@@ -83,6 +84,7 @@ level of information with labels. An issue should have **one** of the following
 
 Issues are closed when a resolution has been reached. If for any reason a closed issue seems
 relevant once again, reopening is great and better than creating a duplicate issue.
+-->
 
 ## Everything else