I'd like to enable the workflow where I have a .localjustfile in project directories to store commands for me personally, not intended to be committed to the repository. Simply using .justfile is not sufficient if the project itself uses just, as just will give an error if both .justfile and justfile exist, stating multiple candidates have been found (which makes sense).
Just has the -f, --justfile argument to specify the exact justfile to load, but this does not do the automatic "scan upwards searching for <filename>" behavior of just that nicely lets you run commands from anywhere in the project.
Would you be open to add an argument similar to --justfile, but which instead changes the name just searches for, rather than specifying an exact path?
Or alternatively (but less flexibly) an option --local-justfile which makes just look for localjustfile or .localjustfile.
I'd like to enable the workflow where I have a
.localjustfilein project directories to store commands for me personally, not intended to be committed to the repository. Simply using.justfileis not sufficient if the project itself usesjust, asjustwill give an error if both.justfileandjustfileexist, stating multiple candidates have been found (which makes sense).Just has the
-f, --justfileargument to specify the exact justfile to load, but this does not do the automatic "scan upwards searching for<filename>" behavior ofjustthat nicely lets you run commands from anywhere in the project.Would you be open to add an argument similar to
--justfile, but which instead changes the namejustsearches for, rather than specifying an exact path?Or alternatively (but less flexibly) an option
--local-justfilewhich makesjustlook forlocaljustfileor.localjustfile.