Skip to content

Additional guidelines for how to use Conda focusing on tasks #604

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

Merged
merged 11 commits into from
Mar 20, 2024
Merged

Conversation

YankeMao
Copy link
Collaborator

@YankeMao YankeMao commented Mar 20, 2024

Write the instructions for four major types of tasks of conda, which are Managing conda, Managing environments, Managing channels, and Managing packages. Introduced the guidelines of these four tasks and the commonly used commands for these tasks. This PR is related to the issue: Development Process: Introduction for the Conda #484

…cifically, introduced the basic guidelines for managing conda, managing environment. managing channels. and managing packages with Conda.
Copy link
Collaborator

@emma0925 emma0925 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Yanke, I think your pr looks great. Here are a few suggestions for making it more clear.

  1. Add a few sentences on the high level idea of managing conda in the beginning of the file
  2. You can also consider adding a description for each sub-section like managing environments
  3. Also, I think it would be very helpful to add a table of contents in the begining

…sk type; add a high-level description of each task.
@YankeMao
Copy link
Collaborator Author

YankeMao commented Mar 20, 2024

Hi Yanke, I think your pr looks great. Here are a few suggestions for making it more clear.

  1. Add a few sentences on the high level idea of managing conda in the beginning of the file
  2. You can also consider adding a description for each sub-section like managing environments
  3. Also, I think it would be very helpful to add a table of contents in the begining

Hi Emma, thank you for your reviewing! I did two major editions to deal with the issue you raised:

  1. Split the file into four separate files where each file contains one type of task.
  2. Add a high-level description at the beginning of each file.

With these changes, now we have high-level descriptions for each type of task. Meanwhile, as we split the file, now each file only had one type of task, which made the file length much shorter than before. Therefore, the table of contents at the beginning is not necessary in this case.

@YankeMao YankeMao closed this Mar 20, 2024
@YankeMao YankeMao reopened this Mar 20, 2024
emma0925 and others added 6 commits March 19, 2024 22:30
Change the point titles into Boldface. Correct punctuation
Change the point titles into Boldface. Correct punctuation
Change the point titles into Boldface. Correct punctuation
Change the point titles into Boldface. Correct punctuation
Copy link
Collaborator

@emma0925 emma0925 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@YankeMao YankeMao merged commit 2932eed into main Mar 20, 2024
@YankeMao YankeMao deleted the Vector branch March 20, 2024 03:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants