Better github workflow

[shiryz]

Let me start by saying, the workflow so far has been good :relaxed: but to ensure the best experience :muscle: you should be following these guidelines:

• issues and prs need to be labeled, the QA knows that a pr is ready for review when it's been labeled awaiting-review
• every pr should be linked to one issue, one pr = one issue, which means you need to reference a max of one issue and perhaps the bigger issue that contains it, but that's about it
• every commit should also reference an issue
• prs need a descriptive title and shouldn't include a reference to the issue
• in the description of every pr you'll need to include the reference to what you're working on and add a description of what's been done
  • if you're still working on a pr and you don't want it merged, add a WIP in the description, this way your team/QA would know that the pr is not ready for review
• You need to have your issues prioritised in a way that enables you to work on different things simultaneously
  • If your issues/tasks depend on each other, and you have your changes ready, add a comment in the top of pr's description referencing the first pr and explaining that the QA needs to merge the first pr and then this one
  • once a pr that is blocking others has been merged, you'll need to pull the changes from master into the branch that was blocked, this way the QA doesn't review your code twice

Happy coding :dancing_women:

[Ryan2601]

Thanks for the time and effort in writing this. It is very helpful. We will make sure to do so starting next week.

[tawfiknasser]

Thanks shiryz, you are helping us a lot :smiley: :+1: :1st_place_medal: