You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A version tagged Level-1 is in the repo(:heavy_check_mark: well done!)
A version tagged Level-2 is in the repo(:heavy_check_mark: well done!)
A version tagged Level-3 is in the repo(:heavy_check_mark: well done!)
A version tagged Level-4 is in the repo(:heavy_check_mark: well done!)
A version tagged Level-5 is in the repo(:heavy_check_mark: well done!)
A version tagged Level-6 is in the repo(:heavy_check_mark: well done!)
A version tagged A-MoreOOP is in the repo(:heavy_check_mark: well done!)
A version tagged A-JUnit-incomplete is in the repo(:heavy_check_mark: well done!)( :warning: The tag is slightly different from the expected value (A-JUnit). Please follow the exact tag in future )
A version tagged A-Jar is in the repo(:heavy_check_mark: well done!)
A version tagged A-Packages is in the repo(:heavy_check_mark: well done!)
A version tagged A-Gradle is in the repo(:heavy_check_mark: well done!)
A version tagged Level-10 is in the repo(:exclamation: try to do by next milestone)
A version tagged A-CheckStyle is in the repo(:heavy_check_mark: well done!)
Fewer than two branches detected in the repo(:exclamation: try to do by next milestone)
You have no tag from categories B/C/D(:exclamation: try to do by next milestone)
At least 2 PRs are in your fork(:exclamation: try to do by next milestone)
Progress of this week
docs/REAME.md is updated(:exclamation: try to do by next milestone)
docs/UI.png has been added(:exclamation: try to do by next milestone)
a jar file has been released in the past week(:exclamation: try to do by next milestone)
Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-09-19 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.
The text was updated successfully, but these errors were encountered:
Leftovers from the previous week
A version tagged
Level-1
is in the repo(:heavy_check_mark: well done!)A version tagged
Level-2
is in the repo(:heavy_check_mark: well done!)A version tagged
Level-3
is in the repo(:heavy_check_mark: well done!)A version tagged
Level-4
is in the repo(:heavy_check_mark: well done!)A version tagged
Level-5
is in the repo(:heavy_check_mark: well done!)A version tagged
Level-6
is in the repo(:heavy_check_mark: well done!)A version tagged
A-MoreOOP
is in the repo(:heavy_check_mark: well done!)A version tagged
A-JUnit-incomplete
is in the repo(:heavy_check_mark: well done!)( :warning: The tag is slightly different from the expected value (A-JUnit
). Please follow the exact tag in future )A version tagged
A-Jar
is in the repo(:heavy_check_mark: well done!)A version tagged
A-Packages
is in the repo(:heavy_check_mark: well done!)A version tagged
A-Gradle
is in the repo(:heavy_check_mark: well done!)A version tagged
Level-10
is in the repo(:exclamation: try to do by next milestone)A version tagged
A-CheckStyle
is in the repo(:heavy_check_mark: well done!)Fewer than two branches detected in the repo(:exclamation: try to do by next milestone)
You have no tag from categories B/C/D(:exclamation: try to do by next milestone)
At least 2 PRs are in your fork(:exclamation: try to do by next milestone)
Progress of this week
docs/REAME.md is updated(:exclamation: try to do by next milestone)
docs/UI.png has been added(:exclamation: try to do by next milestone)
a jar file has been released in the past week(:exclamation: try to do by next milestone)
product website available at http://gabrielseow.github.io/duke (:exclamation: try to do by next milestone)
Note: the above observation was done by the CS2103-feedback-bot and covers changes up to 2019-09-19 00:00:00 only. If you think the above observation is incorrect, please let us know by replying in this thread. Please include links to relevant PRs/comments in your response.
The text was updated successfully, but these errors were encountered: