This site is from a past semester! The current version will be here when the new semester starts.

Week 3 [Fri, Jan 20th] - Project

iP:

Do any leftover iP tasks from the previous week
Add Increments (+ commit, tag, push): Level-1, Level-2, Level-3, A-CodingStandard

tP:

iP

Reminder about the deadline for the weekly project tasks:

Remember to do any leftover increments from the past weeks before starting on the current week's increments. This guideline applies to future weeks too.

Implement the given below in the given order.

From this point onward, after completing each increment,
- git tag the commit with the exact increment ID e.g., Level-2, A-TextUiTesting
  
  Git tags are not the same as Git commit messages.
- git push the code to your fork
  
  Git doesn't push tags unless you specifically ask it to. After pushing a tag to your fork, you should be able to see that tag by visiting https://github.com/YOUR_USER_NAME/REPO_NAME/tags e.g., https://github.com/se-edu/addressbook-level3/tags
  
  If you encounter issues connecting Sourcetree with your GitHub account, refer to these Sourcetree Tips.
Remember to take note of our plagiarism policies, if you haven't done so already:

Q. How are the iP git tags used in grading?

Q. What if I discovered a bug after I finished an increment?

Q. I did multiple increments in the same commit. How to fix?

Q. The requirements of an increment scheduled for this week is already satisfied by the work I did in an earlier week. What now?

Q. My iP increments are not detected by the dashboard because I forgot to push my tags earlier. What now?

Q. Oh no! I made a mistake in my tag/branch name.

Duke Level-1: Greet, Echo, Exit

Duke Level-2: Add, List

Duke Level-3: Mark as Done

Duke A-CodingStandard: Follow the Coding Standard

After forming teams, set up a weekly project meeting time/venue (and communication channels) with your team members: