Tags: pyiron/actions
Tags
Patch hatch-release (#159) * Target branch Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Don't fail at git inspection E.g. in case there are zero tags. Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> --------- Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com>
Actions 4.0.9 (#158) * Fix bash typo Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Add git information to action output Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Re-target branch Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Fetch more So we have full access to tags, etc. Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Just delete any pre-existing version file Hatch is going to overwrite it anyhow, and it shouldn't be tracked since hatch writes it dynamically. Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> --------- Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com>
🐛 target inputs (#155) * 🐛 reference inputs To ensure defaults removal happens Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Target branch Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Fix formatting Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> --------- Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com>
Allow multiple test directories (#154) * Allow multiple test directories In the unit-test action, and propagate the docstring change up through the tools that depend on this. This gives finer-grained control for which tests to run where (in particular, to exclude the benchmark tests from the coverage run, if you want) Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Convert the input var to a bash iterable Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Target branch Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> --------- Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com>
Actions 4.0.6 (#153) * Target branch Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Write a workflow for releasing with hatch Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Use python to scrape the toml file Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Single-line the python My script is having trouble parsing the python sub-script Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Allow the version file to not exist Hatch will generate it automatically, but if a user has something there, ignore it (and print a warning) Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> --------- Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com>
Add an optional mypy job (#152) * Add an optional mypy job Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Bump tag Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> --------- Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com>
More python control (#151) * Add python paths in more jobs All the ones where we are running our local code. Also bumping the tag Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Add python version to setup of linters Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> --------- Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com>
Let add-to-python-path add for Windows (#150) * Target latest Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Modify for windows path adjustments Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Add log statement Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> --------- Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com>
[patch] Limit coverage env (#147) * Target branch Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Disable coverage env When we're not calculating coverage Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Target the next tag Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> --------- Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com>
[patch] Use codecov (#146) * Target branch Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Include codecov as an option for coverage And make the language more generic now that there are two paths Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Break apart the coveralls and codacy envs Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Manage coveralls and codacy dependencies by boolean So that the upstream callers can turn them on or off. If users want some non-standard version, they already have the freedom to add these via the `env-files` argument, we anyhow only really needed these input fields to access the default stored env file, so a boolean is completely ok! Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Reinstate the removed args And change the default of the new args to maintain backwards compatibility Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Combine input args To match the original for compatiblity Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Fill in final target I must have overwritten this replacement somehow? Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Normalize path separators Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Move slash Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Print paths Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Normalize the standard env path too This is the one which actually provides coverage Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Actually forward the codecov input Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> * Target the next release Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com> --------- Signed-off-by: liamhuber <liamhuber@greyhavensolutions.com>
PreviousNext