Add conda-smithy version to conda-forge.yml
See original GitHub issueJust as the title says, we should add the conda-smithy
version to conda-forge.yml
so that we can tell what version we re-rendered (or rendered) with.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Using conda-smithy to manage your CI
By adding a recipe/ directory to your repository, the conda-smithy command ci-skeleton lets you hook into well-tested and robust CI infrastructure. Using the ......
Read more >conda-forge/conda-smithy: The tool for managing ... - GitHub
conda -smithy is a tool for combining a conda recipe with configurations to build using freely hosted CI services into a single repository,...
Read more >Creating Packages — docs documentation
The recipe may be created based on the meta.yaml file from the respective conda-forge feedstock (and sometimes from the original package repository). If...
Read more >conda-smithy: an easy way to build and deploy your ... - Medium
git clone https://github.com/conda-forge/conda-smithy.gitcd conda-smithyconda install --file requirements. · package: · conda-smithy init recipe.
Read more >Conda Smithy - :: Anaconda.org
conda install. Authentication Prerequisites: anaconda login. To install this package run one of the following: conda install -c conda-forge conda-smithy
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think we can close this one out - it is conceivable to have a version string in the feedstock that is only updated when we re-render and something other than the version number has changed. For now though - I don’t think we need to keep this one open - the commit convention gives feedstock users a reasonably good clue.
I think PR ( https://github.com/conda-forge/conda-smithy/pull/307 ) was right on the money 💰. What we should be doing is standardizing our commits whether we re-render or the bot re-renders to make it easier to see what version we re-rendered with last. After all everything outside of the recipe directory should only be changed by re-renderings.
Beyond that, other tricks like git pre-commit hooks, automated re-rendering PR ( https://github.com/conda-forge/conda-forge-webservices/issues/74 ), and so on can be used make this a trivial nearly mindless background operation.