-
Notifications
You must be signed in to change notification settings - Fork 671
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
Allow CLI to be run without .sonarwhalrc in current directory #718
Comments
I personally agree that we should do that. (I don't remember why we didn't do it that way in the first place 🤔)
As long as we make it clear (with an appropriate warning/note as you specified), I'm personally ok with it. @sonarwhal/core Thoughts? |
@poshaughnessy, @diekus, @torgo I was discussing this issue with @molant, and we think this can be a good first issue to solve that will also allow you to better understand how Do any of you want to take this issue? We can help you along the way! |
@alrra Sorry for the delay. If it's not too late, yes, let's give this a try! I'll see how far I get and hopefully can put in an initial PR for review and feedback :) |
Go for it, and don't hesitate to let us know if we can help! |
@poshaughnessy we've separated everything into packages now so if you want to give this a try let us know. Otherwise we will probably take care of this in the next few days. |
Proposal: Given that the recommended use of the CLI is to point to a URL (rather than a local project), I would suggest we do not need to pollute the current directory with a
.sonarwhalrc
file.How about...
.sonarwhalrc
found in the current directory, look for.sonarwhalrc
in user's home directory..sonarwhalrc
found in user's home directory either, proceed with default configuration? (With an appropriate warning / note?). This would have the added benefit of reducing a necessary step (sonarwhal init
) for first time users to try out the CLI.(This may be related to #713?)
The text was updated successfully, but these errors were encountered: