Support different time periods for different repos for report-config.yaml

[lyuanww]

What feature(s) would you like to see in RepoSense

With the the one-stop config feature completed (PR: #2299) , we can enhance the feature by supporting different time periods for different repos for more customisability.

Optimally, the since-date and until-date fields should be optional.

We have already implemented this feature (refer to #2280) for the CSV dates.

Additional context

Will need to take note of resolving conflict for the dates between different configurations (CLI, CSV and report-config.yaml)

Please refer to #2334 for more context.

[lihongong]

Hi, could i work on this issue? Thanks

[CYX22222003]

@lihongong

Sure, we'll be happy to have your help.

If you need info about the setup, workflow, PRs etc, you can check out our developer guide.

Please make sure closely follow the workflow when making contribution.

However, this task may be a bit challenging as it needs to align with the conflict resolving mechanisms for dates across different configurations. Please refer to the PR #2280 and issue #2334 for more context before making any breaking changes

[lihongong]

Hi @CYX22222003 , in the UG configFiles.md, it says that repo-config.csv supports date in the format of • DD/MM/YYYY • DD/MM/YYYY'T'HH:mm • DD/MM/YYYY'T'HH:mm:ss However, it only supports DD/MM/YYYY when I run it in my computer. Should I support all 3 formats in report-config.yaml and fix the implementation of RepoConfigCsvParser as well?

[lihongong]

Hi @CYX22222003, sorry for the late comment, please review my PR here. Thank you.