Code Review-First project

[SabaAhmad404]

Kindly check our Kanban-board

1. https://github.com/SabaAhmad404/javascript-capstone/projects/2
2. We are a group of Three people .
   • Student A : @SabaAhmad404
   • Student B: @george827
   • Student C: @Hassaanjbaig-code

[tresorsawasawa]

STATUS: REQUIRED CHANGES :recycle::recycle:

Hi @SabaAhmad404, @george827, and @Hassaanjbaig-code Good job so far! I know you worked hard to implement this project, I really appreciate the effort you put in! But there are some issues that you still need to work on to go to the next project but you are almost there!

Required changes :recycle: :recycle:

• [ ] As required for the project, make sure all cards are assigned to team members as you did for some of your group task cards. Each card should look something similar in the image below:

• [ ] While assigning cards to team members, you should make sure they are done in a fair way. You need to decide who is Student A, Student B, and Student C. So each card with Student A in its title should always be assigned to the same student (and analogical for other students).

Optional suggestions

• [ OPTIONAL ] I think it would be better if you edit your Kanban board title name to something more meaningful as right now you are still using the same name of the template. You can edit it to something like JavaScript Group Capstone instead of [COPY] [TEMPLATE] JavaScript Group Capstone
• [ OPTIONAL ] I think it would be better if you also edit the edit names of team members by using their GitHub usernames instead. You can make using the same syntax as in the example below:

  - Student A : [@SabaAhmad404](https://github.com/SabaAhmad404)
  - Student B: [@george827](https://github.com/george827)
  - Student C: [@Hassaanjbaig-code](https://github.com/@Hassaanjbaig-code)

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 ping me @tresorsawasawa when you comment so I can receive the notification or use slack with the same name.

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.

[Owusu-Desmond]

Hi @SabaAhmad404 @george827 @Hassaanjbaig-code ,

Your project is complete! There is nothing else to say other than... it's time to merge it :shipit: Congratulations! 🎉

Highlights

📌 Great working on the setup of the project kanban board✅

Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.

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.

---

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.