When running aspect init at a directory that contains a dirty worktree, it fails with the following:
$ aspect init
{"level":"warn","time":"2024-07-03T03:22:20-03:00","message":"working tree is dirty, use --force to apply changes"}
Error: missing scaffold path
Indeed aspect help init does not contain a --force flag, but I think this suggestion is misleading to the user. (My guess is that this message comes from the downstream dependency).
With regards to the scaffold path error message I didn't dig into it, once I had my worktree clean again, it executed successfully.
Version
Development (host) and target OS/architectures: linux_x86_amd64 (WSL2 Ubuntu)
Output of bazel --version: bazel 7.2.1
Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file: N/A
What happened?
When running
aspect init
at a directory that contains a dirty worktree, it fails with the following:Then if I try:
Indeed
aspect help init
does not contain a--force
flag, but I think this suggestion is misleading to the user. (My guess is that this message comes from the downstream dependency).With regards to the
scaffold path
error message I didn't dig into it, once I had my worktree clean again, it executed successfully.Version
Development (host) and target OS/architectures:
linux_x86_amd64 (WSL2 Ubuntu)
Output of
bazel --version
:bazel 7.2.1
Version of the Aspect rules, or other relevant rules from your
WORKSPACE
orMODULE.bazel
file:N/A
Language(s) and/or frameworks involved:
N/A
How to reproduce
Any other information?
No response