<aside> ☝ This is a simple walkthrough of how to use issues for feature planning, task assignment, and discussions.
</aside>
GitHub issues is a simple but useful tool. It can be used for feature tracking, task assignment, and discussions about implementations. More importantly, it can be used to track what needs to be done at a high level.
Every feature should have an issue in the repository, with the corresponding priority tag (P0, P1, P2). Doing this will make it extremely easy to deem project progress. For example, a lead could look at the issues page and think, "oh, we're almost done with all of our P0s! we should start planning P1 feature order."
When you assign a task to someone, you can assign them in the GitHub issue as well. This makes it super easy to keep everything in one place, as relevant PR's will be linked as well. With the same method as above, you can see exactly what features are being worked on and by who.
