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>

Author: robnester-rh

CONTRIBUTING.md

@@ -10,42 +10,42 @@ 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).
-* 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.
+- 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.
 
 The community will then take care of the issue as soon as possible.
 
 ## Reporting Issues
 
 We use GitHub issues to track bugs and errors. If you run into an issue with the project:
 
-* Open an Issue.
-* Explain the behavior you would expect and the actual behavior.
-* Please provide as much context as possible and describe the reproduction steps that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
+- Open an Issue.
+- Explain the behavior you would expect and the actual behavior.
+- Please provide as much context as possible and describe the reproduction steps that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
 
 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. 
-  * 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.
+- The project team will label the issue accordingly.
+- 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.
 
 ## Requesting Features
 
 Enhancement suggestions are tracked as GitHub issues.
 
-* Suggest a single enhancement per issue.
-* Provide a clear and descriptive title for the issue to identify what the specific suggestion is.
-* Provide a step-by-step description of the suggested enhancement in as much detail as possible.
-* Describe the current behavior, the expected one, and why you expect this behavior.
-  * At this point you can also list which alternatives do not work for you.
-* Explain why this enhancement would be useful to other users.
-  * You may also want to point out the other projects that solved it "better" and could serve as inspiration.
+- Suggest a single enhancement per issue.
+- Provide a clear and descriptive title for the issue to identify what the specific suggestion is.
+- Provide a step-by-step description of the suggested enhancement in as much detail as possible.
+- Describe the current behavior, the expected one, and why you expect this behavior.
+  - At this point you can also list which alternatives do not work for you.
+- Explain why this enhancement would be useful to other users.
+  - You may also want to point out the other projects that solved it "better" and could serve as inspiration.
 
 ## Submitting Changes
 
@@ -65,11 +65,11 @@ All changes must come from a pull request (PR) and cannot be directly committed.
 
 Before a pull request can be merged:
 
-* The content of the PR has to be relevant to the PR itself
-* The contribution must follow the style guidelines of this project
-* Multiple commits should be used if the PR is complex and clarity can be improved, but they should still relate to a single topic
-* For code contributions, tests have to be added/modified to ensure the code works
-* There has to be at least one approval
-* The feature branch must be rebased so it contains the latest changes from the target branch
-* The CI has to pass successfully
-* Every comment has to be addressed and resolved
+- The content of the PR has to be relevant to the PR itself
+- The contribution must follow the style guidelines of this project
+- Multiple commits should be used if the PR is complex and clarity can be improved, but they should still relate to a single topic
+- For code contributions, tests have to be added/modified to ensure the code works
+- There has to be at least one approval
+- The feature branch must be rebased so it contains the latest changes from the target branch
+- The CI has to pass successfully
+- Every comment has to be addressed and resolved