iP: Week 3

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

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.

From this point onward, after completing each increment,
- git tag the commit that completed the increment with the exact increment ID e.g., Level-2, A-TextUiTesting
  Git tags are not the same as Git commit messages.
```
%%{init: { 'theme': 'default', 'gitGraph': {'mainBranchName': 'master'}} }%%
gitGraph
  commit id: "..."
  commit id: "Rename main class"
  commit id: "Add greeting" tag: "Level-0"
  commit id: "Add support for echo"
  commit id: "Fix bug in echo" tag: "Level-1"
  commit id: "Add support for list"
  commit id: "Add support for bye"
```
- 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 this Sourcetree Tutorial.
The relevant textbook topics are:
- Git-Mastery → Lesson: T1L5. Saving a Snapshot
- Git-Mastery → Lesson: T2L5. Updating the Remote Repo
- Git-Mastery → Lesson: T4L2. Tagging Commits

Duke Level-1: Echo

Duke Level-2: Add, List

Duke Level-3: Mark as Done

Duke A-CodingStandard: Follow the Coding Standard

FAQ What to do if a certain aspect is not covered by the Java/Git standard?