search

nus-cs2103-AY2223S2 / forum

12 stars 0 forks source link

Importance of Proper RepoSense #268

Closed francisyzy closed 1 year ago

francisyzy commented 1 year ago

From the module website, it says that we should keep track of authorship of code. This may cause additional rigor if we have to use @@author tags everywhere. How important is this component, should we just use git history for tagging instead?

https://nus-cs2103-ay2223s2.github.io/website/admin/tools.html#tool-reposense-for-authorship-tracking

francisyzy commented 1 year ago

Nice try ChatGPT

Screenshot 2023-03-20 at 1 45 15 AM image

damithc commented 1 year ago

Nice try ChatGPT

Yup :-p

damithc commented 1 year ago

From the module website, it says that we should keep track of authorship of code. This may cause additional rigor if we have to use @@author tags everywhere. How important is this component, should we just use git history for tagging instead?

https://nus-cs2103-ay2223s2.github.io/website/admin/tools.html#tool-reposense-for-authorship-tracking

@francisyzy normally, you don't need to track authorship manually using @@author tags. RepoSense does that automatically using Git data. You only need to use @@author tags when you want to override the authorship allocation RepoSense generates based on Git data. You can do this closer to the final submission. In most cases, the authorship allocation generated by RepoSense will be close enough in which case you can let it be.

francisyzy commented 1 year ago

Thanks prof! Will close the issue in a couple of days so that people can see this question!