Remove issue link from CONTRIBUTING.md

Removed issue link from CONTRIBUTING.md as this file is repository
agnostic.

Signed-off-by: Rob Nester <rnester@redhat.com>

CONTRIBUTING.md

@@ -10,11 +10,11 @@ Please, make sure you read both of them before contributing, so you can help us
 
 ## Requesting Support
 
-Before you ask a question, it is best to search for existing [issues](https://github.com/enterprise-contract/ec-cli/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
+Before you ask a question, it is best to search for existing issues that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
 
 If you then still feel the need to ask a question and need clarification, we recommend the following:
 
-* Open an [issue](https://github.com/enterprise-contract/ec-cli/issues/new).
+* Open an issue.
 * Provide as much context as you can about what you’re running into.
 * Provide project and platform versions (golang, operator-sdk, etc), depending on what seems relevant.
 
@@ -31,7 +31,7 @@ We use GitHub issues to track bugs and errors. If you run into an issue with the
 Once it’s filed:
 
 * The project team will label the issue accordingly.
-* A team member will try to reproduce the issue with your provided steps. 
+* A team member will try to reproduce the issue with your provided steps.
   * If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-reproducer`. Bugs with this tag will not be addressed until they are reproduced.
 * If the team is able to reproduce the issue, it will be marked `needs-fix` and left to be implemented by someone. Other labels can be used in addition to better describe the issue or its criticality.