All the course activities are scheduled to be in-person activities this semester.

iP: Week 5iP: Week 7


iP: Week 6

  1. Add Increments as parallel branches: Level-6, Level-7
  2. Add Increment: A-Jar

1 Add Increments as parallel branches: Level-6, Level-7

  • Practice using parallel git branches, as explained below:
    1. First, do Level-6 in a branch named branch-Level-6, but do not merge it.
    2. Then, go back to the master branch and implement Level-7 in a separate branch named branch-Level-7.
    3. Now, go back to the master branch and merge the two branches one after the other.
      If there are merge conflicts, you'll have to resolve them first.
    4. As before, tag the commit (in the master branch, after merging) that achieves the respective deliverable, and push to your fork.
  • As before, Merge without a fast-forward so that git creates a separate commit for the merge.
    Advanced git users: do not delete the branch after merging.
Duke Level-6: Delete
Duke Level-7: Save

FAQ Can I use other data formats (e.g., serialized objects) to save tasks?

FAQ Oops, I messed up my branching! Will I be penalized?

FAQ What if I did the increment in the master branch, not in branch-___ as required?

2 Add Increment: A-Jar

Duke A-Jar: Create a JAR File

Note that if A-Jar increment does not require any code changes, you may tag the commit at which this was achieved as A-Jar (even if that commit has another tag already). Otherwise, tag the latest commit as usual. In both cases, push the tag to the fork.


iP: Week 5iP: Week 7