-
Notifications
You must be signed in to change notification settings - Fork 297
install: switch from mamba init to conda init
#1393
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
Conversation
$ mamba init bash The following arguments were not expected: bash init Run with --help for more information.
|
π Thanks for opening this pull request! Please check out our contributing guidelines. π |
Reviewer's GuideUpdated the installation guide to reflect the correct Mamba initialization command. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated installation instructions to recommend mamba and corrected conda initialization command.
mamba init to conda init
|
You are right @WFFWJH that With the latest miniforge3, running Testing the recommended initiation from the miniforge readme page as |
|
π π π Congrats on merging your first pull request! We here at behaviorbot are proud of you! π π π |
when I execute "mamba init bash", I got error like this:
$ mamba init bash
The following arguments were not expected: bash init Run with --help for more information.
I read "mamba -h", so I change "mamba init bash" to "mamba shell init" follow the result.
Summary by Sourcery
Documentation: