You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to run a recipe in a bakery, it will need a unique name. Some questions come to mind. I imagine that the unique identifier for a recipe once it is stored will be something like
{github_org}/{github_repo}/{recipe_name}
In most cases, <github_org> will be pangeo-forge and the repo will be the name of the feedstock repo. This structure allows us to have multiple recipes in one repo, as long as they have distinct names.
Is a name always required to initialize a recipe? They are currently not and things work fine.
What naming conventions should the name require?
How shoud ci and linting validate the name?
The text was updated successfully, but these errors were encountered:
In order to run a recipe in a bakery, it will need a unique name. Some questions come to mind. I imagine that the unique identifier for a recipe once it is stored will be something like
{github_org}/{github_repo}/{recipe_name}
In most cases,
<github_org>
will bepangeo-forge
and the repo will be the name of the feedstock repo. This structure allows us to have multiple recipes in one repo, as long as they have distinct names.The text was updated successfully, but these errors were encountered: