https://github.com/Izebiafe/BleFi

[Izebiafe]

Note for Reviewer:

There are two people in our team.

Team members @Izebiafe @blessing-michael.

Here is a link to the project: https://github.com/Izebiafe/BleFi/projects/1

[levy002]

Hello @Izebiafe

While you made a great effort in this project, unfortunately, I cannot proceed to review your code.

Invalid Code Review Request

You have submitted a project, that doesn't have a link to your Kanban project.

Kindly make sure to add the link to your Kanban Project.

Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏

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.

---

Invalid Code Review Request does not count into the code reviews limit.

[julie-ify]

Hi @Izebiafe,

While you made a great effort in this project, unfortunately, I cannot proceed to review your code.

Invalid Code Review Request

• You have not added the link to the Kanban board project.

Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏

Cheers and Happy coding!👏👏👏

Feel free to leave any questions or comments in the PR thread if something is not 100% clear.

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.

---

Invalid Code Review Request does not count into the code reviews limit.

[HAMMAS-SALEEM]

Invalid Submission :red_circle:

Hey @Izebiafe :wave:

Good job on implementing some of the requirements but I cannot proceed review of your pull request because there are some issues that you still need to work on to go to the next project but you are almost there! :blush:

Optional

All the changes with optional tags are not crucial enough to prevent you from getting the approval but we highly recommend to students that they should take these changes into consideration.

Happy coding! :clap: :clap: :clap:

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.

Mandatory Changes ♻️

• [ ] It would be nice if you add the Kanban Board link to your issue summary as suggested by the previous reviewer 👍

[mukhammadrizooff]

Hi @TEAM,

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!

Highlights

• TEAM work ✔️
• Correct GitFlow ✔️
• Good implementations ✔️

Required Changes ♻️

• [ ] [REQUIRED] Good job so far! Cards should be assigned to team members in a fair way:

• Students needed to decide who is Student A, Student B. So each card with Student A in its title should always be assigned to the same student.

All cards are assigned to team members. You should see a circle with the user's avatar on each card. See the example below:

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.

[skyv26]

Hi @Izebiafe and @blessing-michael ,

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

STATUS: APPROVED 🟢

Highlights

• Good PR title ✅
• Descriptive PR description ✅
• Implement the features ✅

Optional suggestions

Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you 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.

⚠️ WARNING ⚠️

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.

Have any doubt ❓

Feel free to leave any questions or comments in the PR thread if something is not 100% clear. Please, remember to tag @skyv26 in your question so I can receive the notification. You can also follow me on the below platforms

---

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.