contribution guide

[Sohieb]

We still don't have any guidelines/rules for contributing to the project.
I'm going to start a new file (guidelines.md) to set the rules for contributing and for the style followed in the project.

Please comment here your ideas about this topic.

[OmarTahoun]

@Sohieeb so we want to have something with the full (fork, create branch, make pull request, ...) and the whole thing or just simple guide lines?

[Sohieb]

the complete workflow (fork, .., pr, etc) + general guidelines like (style guide, naming, etc).

[OmarTahoun]

We can have some thing that goes like this (For contributing):
1: Fork the repo!
2: Clone your fork of the repo: git clone ____
3: Leave comments if you've started working on an issue, leave a comment as it helps avoid duplicate work.
4: Create a branch(whose name reflect the issue you are working on) and make your changes.
5: Run git commit and add your message describing what you have changed. If you have made changes that address an issue include the text Closes #1 (where 1 would be the issue number) to your commit message.
6: Submit Pull request - Once you have committed your changes locally and pushed them to your fork of the repo, a banner with a Compare & pull request button should appear to submit a pull request.

[moadmmh]

Let us avoid Random PR please i have been solving a lot of conflicts recently

[OmarTahoun]

Sorry those were mostly my mistakes