Contributing & Forking Issue

[stacknomad]

So... let's say that I wanted to contribute this project and began forking it. Even after following the contributing guidelines, I'm left with an non-working and broken local project. It would be impossible to make the changes you want to make without having to make more unrelated changes that should have already been there.

Things like, the .env file and a guide to getting that to work with the code, so that any and all secrets required by the project is provided without having to change the main codebase just to get it working for you locally.

Although they are free, you'll have to make accounts in order to get those API keys and secrets needed.

I made the necessary fixes for these issues and also updated the CONTRIBUTING.md file for documentation.

[Vignesh025]

Hi @stacknomad ,

Thank you so much for your valuable feedback and for taking the time to work on the necessary fixes for the project. I really appreciate your initiative in resolving the issues with the .env file and improving the contributing guidelines.

As a suggestion, it would be great if you could focus on making one change per pull request. This will make it easier to review and merge updates one step at a time, ensuring each set of changes is tested thoroughly. For example:

• One pull request could address the fixes for the .env file and related secrets.
• Another pull request could focus on updating the CONTRIBUTING.md file for documentation.

Once you've made these changes, feel free to open the separate pull requests, and I’ll be happy to review them promptly.

Thank you again for your efforts, and I look forward to seeing your contributions!