contributing.md

How to contribute to Parstdex

Did you find a bug?

• Ensure the bug was not already reported by searching on GitHub under Issues.

• If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible or an executable test case demonstrating the expected behavior that is not occurring.

• Please refer to each project's style and contribution guidelines for submitting patches and additions. In general, we follow the fork-and-pull Git workflow.

  • Fork the repo on GitHub
  • Clone the project to your own machine
  • Commit changes to your own branch
  • Push your work back up to your fork
  • Submit a Pull request so that we can review your changes

NOTE: Be sure to merge the latest from "upstream" before making a pull request!

Did you write a patch that fixes a bug?

• Open a new GitHub pull request with the patch.

• Ensure the PR description clearly describes the problem and solution. Include the relevant issue number if applicable.

Do you intend to add a new feature or change an existing one?

• Suggest your change in the suggestion issue.

Do you have questions about the source code?

• Please feel free to ask your questions by mailing authors, and we will document common questions as soon as possible.
  • Sajad Mirzababaei
  • Amir Hossein Kargaran

Thanks! ❤️ 🌻 🌸

Parstdex Team

Credits

Big thank you to all the people who have already contributed to PARSTDEX!

Amir Hossein Kargaran, Sajad Mirzababaei, Hamid Jahad