Progress Dashboard not detecting A-Jar tag/release

[SimJunYou]

So far, I've made a release on my repo for the jar file and tagged it with the A-Jar tag. Is there anything else I'm missing out?

For context, I made the Level-6, Level-7, and A-Collections increments on the same day and they were marked on the Dashboard as complete.

[AndreWongZH]

It seems like your version 1.0 is listed as a pre-release or maybe the progress dashboard is not updated yet.

[okkhoy]

can you remove the pre-release label?

[adinata15]

I also experienced the same case for my Level-4, I have tagged Level-4 on 30th August (Week 4) but it is not registered on the progress dashboard. However, the rest of the tag such as A-UiTesting and A-CodeQuality are registered. On Github: On Progress details:

[wangqinNick]

Same here. The branch level-5 is not detected on ip progress dashboard, though the tag is detected.

The tag for Level-5,6,7 are all not detected on RepoSense Report, but they are detected on the ip progress dashboard.

[zhixiangteoh]

have you pushed the tags, like

git push —tags?

— is two ‘-‘s

[okkhoy]

@wangqinNick you don't have a branch called branch-level-5 in your IP repo

@adinata15 and @f0fz you have a slightly stranger problem

Go to the tags/release and click on the commit listed to view the details:

According to GitHub, this can happen due to a few reasons e.g., force push, un-merged merge conflict commit etc., Since the script cannot trace back to this commit, it was not detected. You can try to tag some other commit in your repo after the level was completed and push the new tag.

[Edit] Ack: Thanks to Prof. Damith for helping me figure this out!

[wangqinNick]

@wangqinNick you don't have a branch called branch-level-5 in your IP repo

@adinata15 and @f0fz you have a slightly stranger problem

Go to the tags/release and click on the commit listed to view the details:

According to GitHub, this can happen due to a few reasons e.g., force push, un-merged merge conflict commit etc., Since the script cannot trace back to this commit, it was not detected. You can try to tag some other commit in your repo after the level was completed and push the new tag.

[Edit] Ack: Thanks to Prof. Damith for helping me figure this out!

I forgot to push the branch level 5 to the remote. Thanks very much

[adinata15]

@wangqinNick you don't have a branch called branch-level-5 in your IP repo

@adinata15 and @f0fz you have a slightly stranger problem

Go to the tags/release and click on the commit listed to view the details:

According to GitHub, this can happen due to a few reasons e.g., force push, un-merged merge conflict commit etc., Since the script cannot trace back to this commit, it was not detected. You can try to tag some other commit in your repo after the level was completed and push the new tag.

[Edit] Ack: Thanks to Prof. Damith for helping me figure this out!

Thank you for the help @okkhoy ! I have deleted the old tag and pushed a new tag of "Level-4" into my repo. Just wondering, will we be deducted marks for this?

[okkhoy]

Probably won't affect your IP marks by itself.