Feature request: `use_just()` to add a minimal `justfile` for project tasks

[Yousa-Mirage]

Hi, I’d like to ask whether a small helper like use_just() would be considered in scope for usethis.

The idea would be simple: create a minimal justfile in the project root, similar to how use_make() creates a Makefile.

Motivation

just is a command runner that is increasingly used as a lightweight, cross-platform way to define common project tasks such as:

• running tests
• rendering documentation
• formatting code
• checking packages
• building site or pkgdown output

Compared with Makefile, a justfile can be easier to read and adopt for users who are not already familiar with make, especially on Windows or in mixed OS teams.

Since usethis already provides helpers for setting up common project/developer infrastructure, a use_just() helper seems like a natural extension for teams and package authors who prefer just as their task runner. For those users, a use_just() helper could provide a convenient way to initialize a justfile with a very small starter template.

Possible scope

I imagine use_just() as a deliberately small feature:

• create a justfile in the project root if it does not already exist
• add a minimal template
• avoid enforcing a large or opinionated set of recipes

For example, the generated initial template could be as small as:

default:
    @just --list

so that users can extend it themselves.

Question

Would a helper like this be considered a good fit for usethis?

If this seems potentially in scope, I’d be happy to draft a PR.

[jennybc]

Thanks, but I'm afraid this is not a great fit, given our current workflows, i.e. we don't use just in R packages (I have used just elsewhere). Below is a saved reply that explains my response, since this is a lesson we have learned the hard way.

---

(THING = just)

This seems like an interesting idea, but we (usethis maintainers, tidyverse/r-lib team) don't currently use THING ourselves. Our experience adding usethis features that we don't use personally has not been good. These features are especially vulnerable to bit rot, since we won't notice problems in a timely manner and we lack motivation and context when work is needed. This can then lead to a negative experience for new users.

Thanks again for the suggestion, but we've learned everyone is better off if we identify a lack of fit in advance.