docs: linking contribution guide

Signed-off-by: Sienna Chien <siennac@Siennas-MacBook-Air.local>

Author: Sienna Chien

CONTRIBUTING.md

@@ -8,58 +8,11 @@ We can't wait to collaborate with you!
 
 ## Contributing Code
 
-### Developer's Guide
-
-Please follow our [Developer's Guide](./docs/dev-guide.md) where you can find comprehensive instructions
-for common development operations.
-
-### Issues
-
-Prioritization for pull requests is given to those that address and resolve existing GitHub issues. Utilize the available issue labels to identify meaningful and relevant issues to work on.
-
-If you believe that there is a need for a fix and no existing issue covers it, feel free to create a new one.
-
-As a new contributor, we encourage you to start with issues labeled as good first issues.
-
-Your assistance in improving documentation is highly valued, regardless of your level of experience with the project.
-
-To claim an issue that you are interested in, kindly leave a comment on the issue and request the maintainers to assign it to you.
-
-### Committing
-
-We encourage all contributors to adopt [best practices in git commit management](https://www.futurelearn.com/info/blog/telling-stories-with-your-git-history) to facilitate efficient reviews and retrospective analysis. Your git commits should provide ample context for reviewers and future codebase readers.
+Please follow the [Contribution guide](https://github.com/kagenti/kagenti/blob/main/CONTRIBUTING.md#contributing-to-this-project) as found in the Kagenti Repository for instructions on how to contribute to our repositories. 
 
-A recommended format for final commit messages is as follows:
-
-```text
-{Short Title}: {Problem this commit is solving and any important contextual information} {issue number if applicable}
-```
-
-### Pull Requests
-
-When submitting a pull request, clear communication is appreciated. This can be achieved by providing the following information:
-
-- Detailed description of the problem you are trying to solve, along with links to related GitHub issues
-- Explanation of your solution, including links to any design documentation and discussions
-- Information on how you tested and validated your solution
-- Updates to relevant documentation and examples, if applicable
-
-The pull request template has been designed to assist you in communicating this information effectively.
-
-Smaller pull requests are typically easier to review and merge than larger ones. If your pull request is big, it is always recommended to collaborate with the maintainers to find the best way to divide it.
-
-See the [making PR](./docs/dev-guide.md#making-a-pr) document for detailed instructions.
-
-## Licensing
-
-Kagenti is [Apache 2.0 licensed](LICENSE) and we accept contributions via
-GitHub pull requests.
+### Developer's Guide
 
-Please read the following if you're interested in contributing to Kagenti.
+Please follow our [Developer's Guide](https://github.com/kagenti/kagenti/blob/main/docs/dev-guide.md#developers-guide), as found in the Kagenti Repository, where you can find comprehensive instructions for common development operations.
 
-## Certificate of Origin
+Please note that the section concerning pre-commit does not apply to this repository. 
 
-By contributing to this project you agree to the Developer Certificate of
-Origin (DCO). This document was created by the Linux Kernel community and is a
-simple statement that you, as a contributor, have the legal right to make the
-contribution. See the [DCO](DCO) file for details.