Update contributing.md

[felipepaes]

Summary

The contributing.md documentation is currently outdated. There's a possibility of encountering the same error currently occurring in the CI when setting up our development environment, so this issue may be related to #1.

Documentation Page Link

https://github.com/osl-incubator/conda-forge-warning/blob/27009c6141236b6b2a3a4103733ac202f2868b24/docs/contributing.md

Code of Conduct

• I agree to follow the Code of Conduct

[felipepaes]

Will be documenting the steps we have used during setup:

• There's no mentioning about the miniforge requirement
• Add the step to use mamba when creating the environment with conda/dev.yaml environment file
• Activate conda environment (conda activate cf-warning)
• Install dependencies with poetry (poetry install) with conda cf-warning env active
• copy .env.tpl as .env and add GITHUB_TOKEN= (it's a good a ideal to link github documentation on token generation)
• run makim tests.unittest
• if everything works, congratulations 🎉

[felipepaes]

Hey @tintayadev! 👋
Just an update on that issue from yesterday
After generating a github token, my tests have run just fine.

This may be related to the scope from you generated token, we may have to mention it on contributing.md as well.

Here is a reference image:

So maybe you can play with the scopes from your generated gh token or maybe delete your old gh token and generate a new one

[tintayadev]

Oh I see, I'll check on that right now 😅
Thanks for letting me know