Meltrust
commented
1 year ago Hi @Carshy,
Good job so far! There are some issues that you still need to work on to go to the next project but you are almost there!
To highlight:
- All tasks have been pointed.βοΈ
Required Changes β»οΈ
- [ ] Kindly add a screenshot of your Kanban board to this issue's description, so we comply with this requirement:
Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
Cheers and Happy coding!πππ
Feel free to leave any questions or comments in the PR thread if something is not 100% clear. Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.
As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.
Carshy
In the current project, our team prepared a Kanban board with a GitHub project(Football Ticketing App). We used no template but rather translated project requirements to cards, which is something we believe we will do regularly when we're working as a developers. The Kanban board showcases a list of tasks assigned to each member and ones done by the group. We are a team of four: Simba Wangu, Michael Adetunji, Collins Musoko, and Johnson Emmanuel. Below is the link to our Kanban board:
https://github.com/users/Carshy/projects/1
Below are two screenshots for the Kanban board