Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setup Kanban Board #13

Closed
KanzaTahreem opened this issue Feb 6, 2023 · 2 comments
Closed

Setup Kanban Board #13

KanzaTahreem opened this issue Feb 6, 2023 · 2 comments

Comments

@KanzaTahreem
Copy link
Owner

KanzaTahreem commented Feb 6, 2023

Hey Reviewer 馃憢

Regarding this issue, we covered the following project requirements 馃斀

  • Create an empty repository for your group project.
  • Open the GitHub project (Kanban board) in your team repo
  • Create tasks on your Kanban board based on the project requirements.
  • Each task should be a separate card with descriptive title and number of points in the [Xpt] prefix
  • Each of the team members should assign themselves to the cards.
  • Decide who will be the assignee for the cards marked as group tasks. All cards on your Kanban board should have assignees.
  • Open a new issue in your repository and send it for review

Project Link 馃敆

Here is the link for Kanban board created for the project

Group Members 馃槃

@rbreva
@KanzaTahreem

@cynthiainga
Copy link

Hi @KanzaTahreem & @rbreva,

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

  • Descriptive issue 鉁旓笍
  • Setup correctly the Kanban board 鉁旓笍

Required Changes 鈾伙笍

Optional suggestions

Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you 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.

@Mihndim2020
Copy link

STATUS: APPROVED!!! 馃帀 馃帀 馃帀 馃嵕 馃嵕 馃嵕

Hi Team,

Good job !!!

To Highlight! 馃憦 馃煝

鉁旓笍 Good job with issue summary

Your project is complete! Great work on making the changes requested by the previous reviewer. There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 馃帀 馃帀 馃帀 馃嵕 馃嵕 馃嵕

Congratulations-Memes-FEATURED

Optional suggestions

Check the comments under the review.

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.

N/A

Cheers and Happy coding!馃憦馃憦馃憦

Feel free to leave any questions or comments in the PR thread if something is not 100% clear or you can get to me on slack using this handle @Mihndim.


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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants