Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove support for standalone config files #2171

Open
damithc opened this issue Mar 25, 2024 · 2 comments
Open

Remove support for standalone config files #2171

damithc opened this issue Mar 25, 2024 · 2 comments

Comments

@damithc
Copy link
Collaborator

damithc commented Mar 25, 2024

This feature https://reposense.org/ug/customizingReports.html#get-target-repos-to-provide-more-info is not used that much. In fact, I'm not sure if it is a good idea to let the repo control a report.

Perhaps we can remove it, to ease our code maintenance?

@sopa301
Copy link
Contributor

sopa301 commented Apr 15, 2024

This will be a breaking change, so the release resolving this issue needs to be a major release.

@ckcherry23
Copy link
Member

This change would make #430 irrelevant, as it discusses priority order between standalone config, CLI arguments and csv configs, and standalone configs will not be supported anymore. However, discussions there would still be useful to make a decision regarding priorities for the one-stop config file in #2161 and the csv config files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants