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
By that, I mean when things like black or pytest have particular arguments, being able to use those (instead of repeatedly being the situation of "why doesn't it work?.... Oh, yeah, I need to ignore such an such a folder when I test...".
A lot of particulars are defined in the ci def file (e.g. ci.yml in github), it'd be nice to reuse these!
So I imagine doing something like this in the terminal
$ isee local PROJECT_ROOT_FOLDER
That would trigger something like:
Extract information from ci definition file (what is extracted can be configured)
Run some processes (parametrized by the info we extracted) locally
The text was updated successfully, but these errors were encountered:
My guess is that this won't be too hard for a basic version.
Specify some patterns that will match the lines that should be extracted
Run these lines (possibly modified to refer to the right project, or after CDing to the right project so that the dot refers to the right folder) using subprocess module.
By that, I mean when things like
black
orpytest
have particular arguments, being able to use those (instead of repeatedly being the situation of "why doesn't it work?.... Oh, yeah, I need to ignore such an such a folder when I test...".A lot of particulars are defined in the ci def file (e.g.
ci.yml
in github), it'd be nice to reuse these!So I imagine doing something like this in the terminal
That would trigger something like:
The text was updated successfully, but these errors were encountered: