- Learn about the project
- Set up prerequisites
- Set up the project in your computer
- Add Increments while committing frequently:
Level-1
,Level-2
,Level-3
,Level-4
,A-TextUiTesting
,Level-5
,Level-6
,A-Enums
Thu, Jan 21st 2359
The iP (and the tP) undergoes changes after each semester. As such, teething issues are a possibility. If you encounter any problem while doing the iP/tP, please post in the forum so that we can take necessary actions.
We discourage you from doing project tasks allocated to future weeks. Reasons: In order to help you gain the ability to apply knowledge or do tasks effortlessly as if you have been doing them for a long timefluency (and also to better simulate real projects), we want the project work to be done at multiple times with time gaps in betweenspaced and spread over a longer period, rather than to be done as a short burst.
Reminder: as per iP grading criteria, some increments need to to be done in each week for you to get full marks.
Please follow instructions carefully. Any deviations can cause our grading scripts to miss your work (and result in you not getting credit for the work).
Deadline:
Note the typical deadline weekly project tasks:
But as there are no tutorials this week, you have until Thu, Jan 21st 2359 to finish this week's iP tasks.
1 Learn about the project
- Read the following two sections, if you haven't done so already:
2 Set up prerequisites
- Ensure you have followed the Preparation sections of the following module tools:
3 Set up the project in your computer
- Read through this week's topics before starting the project.
- Fork https://github.com/nus-cs2103-AY2021S2/ip.
- Enable the issue tracker of your fork (Go to
Settings
of your fork, scroll to theFeatures
section, and tick theIssues
checkbox). Reason: at times we post feedback on your issue tracker.
If the issue tracker is enabled, you should be able to visit the following URLhttps://github.com/{your_user_name}/ip/issues
e.g.,https://github.com/johnDoe/ip/issues
- Clone the fork onto your computer.
- Set up the project in your IDE as explained in the README file.
If you encounter technical problems, follow the guidelines given below in seeking help:
4 Add Increments while committing frequently: Level-1
, Level-2
, Level-3
, Level-4
, A-TextUiTesting
, Level-5
, Level-6
, A-Enums
Thu, Jan 21st 2359
- Implement the following in this context, an increment is a Duke level or a Duke extensionincrements in the given order.
- From this point onward, commit code at important points. Minimally, commit after completing each increment.
- From this point onward, after completing each increment,
git tag
the commit with the exact increment ID e.g.,Level-2
,A-TextUiTesting
git push
the code to your fork ( git doesn't push tags unless you specifically ask it to)