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

Changes to things about packages #79

Draft
wants to merge 102 commits into
base: gh-pages
Choose a base branch
from

Conversation

bobturneruk
Copy link

No description provided.

ns-rse and others added 30 commits February 3, 2023 09:08
I think it would be more helpful to make it clear that `environment.yml` doesn't have to always be used and the
environment files can be called anything. This avoids the possibility of easily over-writing existing files.

I've seen on other projects that people just go with what is in the documentation and create `sample-config.yaml`, which
isn't that helpful as they should be unique to a project so people don't have 384 files all called the same thing.
Notes from an end to end run through on Windows
Closes #8

The text was already there but not visible in the last PR where the need to make this clearer was highlighted. All I've
done is turn it into a Callout with a heading.
Removing references to installing pip in conda envs
Callout for excluding build variant hash
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