casey / casey/just

No way to keep going if one subcommand fails

Open
#2,739 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
Rust
Stars
35.8k
Forks
846
Avg merge
27m
Merged PRs (30d)
3

Description

What GNU Make offers is a command line switch `-k`, or `--keep-going`. What this switch does is it carries on with the build even if one of the dependent makefile targets fails.

I have a justfile containing various long-running tests, and there is also a `test` target having `test1`, `test2`, `test3` as dependants. I am using this top-level targets to have all the tests run overnight or over a weekend. So it would be great if I could supply a command line flag to run all three tests, even if one fails. I don't see any mention of such an option in the helptext, apologies if I missed it!

I'm proposing something like `just -k tests`, or `just --keep-going tests`, in the heritage of what GNU Make does, but feel free to propose a different name or an entirely different solution (like an environment variable?)

Is this something you'd accept a pull request for?

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by reading the existing command-line help and the target-dependency execution behavior, then determine how a `-k` or `--keep-going` option should handle failed dependencies. Done means the chosen behavior is implemented, documented in help text, and verified for a target with multiple dependants.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
build-system, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.