Repository: metacall/core (language: rust)

Issue:
Update on Contributing.md
## 📚 Documentation

An addition to contributing.md which includes an instance (pictorial) to create an issue, so as to help repository first-timers quickly find their way to start contributing on MetaCall.


Discussion / hints:

Fix patch:
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
index bb7fc3123..ea802c726 100644
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -1,7 +1,17 @@
 # Contributing
 
 When contributing to this repository, please first discuss the change you wish to make via issue,
-email, or any other method with the owners of this repository before making a change. 
+email, or any other method with the owners of this repository before making a change. Here is an examplary process you can follow to create an issue on MetaCall:
+
+1. Identify a problem or a possible addition to Metacall codebase/operation<br>
+for instance: ```pre-commit-clang-format not working on windows...```
+2. Then go to the necessary MetaCall gitHub repository and click on the "Issues" tab at the top of the page. Indicate your issue's interest by tagging it as a bug report, custom issue, documentation, feature, or discussion. <br>
+in this case: ```metacall/core```
+3. Type in a title and description for your issue. Be as detailed as possible, including any error messages or steps to reproduce the issue. Image example: <br>
+![issue image](https://user-images.githubusercontent.com/93955843/220493308-0ce3f101-6957-43fb-96d1-7a730ccf304c.PNG)
+
+4. You can assign the issue to yourself, add labels or a milestone to it, and attach files if necessary.
+5. Submit the newly created issue and start working on a solution by creating a fork of the repository. <br>(<a href="https://github.com/metacall/core/issues/370">Here</a> to issue used for explanation)
 
 Please note we have a [Code of Conduct](/.github/CODE_OF_CONDUCT.md), please follow it in all your interactions with the project.
 


Test patch: