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.

Sign up for GitHub

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

Jump to bottom

docs: minor clarity edits on "Available Keys" section; platforms supported #690

Open
2 tasks done
bkreider opened this issue Jun 22, 2023 · 1 comment
Open
2 tasks done

docs: minor clarity edits on "Available Keys" section; platforms supported #690

bkreider opened this issue Jun 22, 2023 · 1 comment
Labels
type::bug describes erroneous operation, use severity::* to classify the type

Comments

@bkreider
Copy link

Checklist

  • I added a descriptive title
  • I searched open reports and couldn't find a duplicate

What happened?

I think this could be put into a "Note box". It is also a little confusing at first for anyone that doesn't know conda-build.

Note that the special environment variables available in meta.yaml when running conda-build are not available here.

Can the documentation add a field platform for the keys that have restrictions on the platform?

Name
required: yes
type: string

Conda Info

No response

Conda Config

No response

Conda list

No response

Additional Context

No response
@bkreider bkreider added the type::bug describes erroneous operation, use severity::* to classify the type label Jun 22, 2023
@jaimergp
Copy link
Contributor

I want to tackle this as part of a migration of the config system to a pydantic model.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type::bug describes erroneous operation, use severity::* to classify the type
Projects
🧭 Planning
Status: 🆕 New
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bkreider @jaimergp