Skip to content

index.md

Latest commit

 

History

History
56 lines (47 loc) · 4.22 KB

index.md

File metadata and controls

56 lines (47 loc) · 4.22 KB
Raw
title: "CS2103DE Software Engineering iP Progress Dashboard"

CS2103DE Software Engineering iP Progress Dashboard

  • Note that the progress shown here is just a rough guidance as it was generated by an automated script. ==A manual inspection will be done after the final submission== to confirm the script's findings.
  • If an increment you did does not appear as 'done' in the dashboard, make sure you have pushed the corresponding tag to your fork and the tag matches the increment name exactly. You can even tag past commits if you forgot to tag those commits earlier or the tag you used differs from the expected tag. The increment will be marked as 'done' at the next script run (it runs once a day). Contact the teaching team ==only if the problem is not rectified even after the next update==.
  • Meaning of colors/icons:
    • %%{{ icon_info }}%% : you can click on this icon to find more info
    • ABC : you have done the corresponding item.
    • ABC : you have done the corresponding item which is an optional item (well done!).
    • !ABC : item overdue, not done yet.
    • !ABC : item due soon, not done yet.
    • !ABC : optional item due soon, not done yet.
  • If you have queries about the data shown in this page, please email pranat@nus.edu.sg and zikun@nus.edu.sg.
  • This dashboard is updated {{ "every 2-3 days" if tic4002 else "daily" }}.
  • Troubleshooting:

Try these steps, and wait till the next dashboard update to see if they turn green as expected.

  1. Go to https://github.com/YOUR_USER_NAME/ip/tags. It should look like this:

    Confirm the tag in question is listed there. If it is not listed, here are the possibilities:
    • You created the tag but never pushed it.
      Remedy: You need to push the tags (pushing a branch doesn't automatically push tags in it).
    • You might have mixed up commit messages and tags, and used the tag name as a commit message instead).
      Remedy: Create the tag
  2. If the tag in question appears in the list, click on the commit hash shown just below it (e.g. :octicon-commit: b6e91a0). This brings you to a page containing commit details.
    • Confirm the commit is in the masterbranch. An example is shown below. Only tags in the master branch are detected by the dashboard.

      Remedy: Wait till the branch that has the tag is merged to the master branch, push the master branch to the fork.
    • Ensure a warning message like the following doesn't appear at the top of the page.

      If it does, most likely you pushed the tag to the fork, but not the commit it belongs to.
      Remedy: Push the commit to the fork, and confirm the warning does not appear anymore.
  1. Go to https://github.com/YOUR_USER_NAME/ip/branches/active. It should look like this:

    Confirm the branch in question is listed there. If it is not listed, push the branch to the fork.
  2. Note the numbers n|m shown for each branch. If the m is not zero, that means the branch is ahead of the master branch by that number of commits, and hence, not considered fully merged (only merged branches are detected by the dashboard). Reasons:
    • You did not push the branch after merging it.
      Remedy: After merging a branch to the master branch, you need to push both branches to the fork.
    • You pushed commits to the branch after merging it to the master branch.
      Remedy: Either delete those extra commits from the branch (both locally and in the fork) or merge the branch to the master branch again.