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
I love the new inspect_artifacts stage, it's great to see what ends up in various outputs within the respective CI run! 👏
I'm wondering thought bout displaying all the recipe content that's under /info - I think this information is pretty useless (it's readily available in the feedstock anyway), and it blows up the inspection stage unnecessary. For example, even a completely empty metapackage gets:
And in multi-output recipes, every output gets a copy of that redundant information... I think it'd be much more preferable to just remove anything under /info, or at least make it opt out. Looking at the implementation here and in conda-package-handling, this will probably need some feature-work there (unless we do some regex-filtering on the output of list_contents).
I love the new
inspect_artifacts
stage, it's great to see what ends up in various outputs within the respective CI run! 👏I'm wondering thought bout displaying all the recipe content that's under
/info
- I think this information is pretty useless (it's readily available in the feedstock anyway), and it blows up the inspection stage unnecessary. For example, even a completely empty metapackage gets:And in multi-output recipes, every output gets a copy of that redundant information... I think it'd be much more preferable to just remove anything under
/info
, or at least make it opt out. Looking at the implementation here and in conda-package-handling, this will probably need some feature-work there (unless we do some regex-filtering on the output oflist_contents
).CC @jaimergp
The text was updated successfully, but these errors were encountered: