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 just hit a problem when my local Runic (v1.0) did one correction that was reverted by the repo CI's Runic (v1.1). That would be nice to make sure don't happen IMO.
Would it be an idea to allow specifying the Runic version in the yaml of the pre-commit, and then either (configurable?) error or warn if the one in @runic doesn't match?
Allow the pre-commit to use a project-local environment with a checked in manifest in a subdirectory instead of the shared environment?
The text was updated successfully, but these errors were encountered:
The latest version of pre-commit support Julia as a language (pre-commit/pre-commit#3348). With that pre-commit will use it's own package environment and install Runic automatically so no need to involve @runic at all.
I just hit a problem when my local Runic (v1.0) did one correction that was reverted by the repo CI's Runic (v1.1). That would be nice to make sure don't happen IMO.
Specific PR: Ferrite-FEM/Ferrite.jl#1161
Two ideas for solution
Would it be an idea to allow specifying the Runic version in the yaml of the pre-commit, and then either (configurable?) error or warn if the one in
@runic
doesn't match?Allow the pre-commit to use a project-local environment with a checked in manifest in a subdirectory instead of the shared environment?
The text was updated successfully, but these errors were encountered: