Lars Kellogg-Stedman

That is surprising! What a bummer.

Well now I feel stupid for not even thinking about that because I deal with multi-document YAML files *all the time* and never even considered that. But even ignoring that...

> For what it's worth I always work using the /out directory in the naml repository. Ah, I see. The README wasn't clear that the `out` directory was created inside...

The typical way of solving this is to pass the `--no-block` flag to systemctl, e.g., ``` systemctl --no-block start docker ``` This will enqueue the start request and return immediately....

As a workaround: ``` current=$(git branch --show-current) git checkout -f $(stg id $(stg next)) git checkout $current stg push ```

> I'm having a hard time reproducing this issue. Here's a complete reproducer: ``` #!/bin/sh rm -rf stgit-example-193 git init stgit-example-193 cd stgit-example-193 cat > README.md file2 stg add file{1,2}...

@jpgrayson just wanted to follow up and see if that last comment helped clarify things?

> Let me know if I'm missing other use cases of --force. The problem I see is that if there are a large number of conflicting files, the cleanup may...

The problem appears to be in `src/alias.rs`, where an `Alias` is defined as: ``` pub(crate) struct Alias { pub kind: AliasKind, pub name: String, pub command: String, } ``` If...

> Please don't add $ to the examples @KnVerey I'm not sure what you want to do with something like this: ``` $ ls -C1 $MYAPP cmGenerator.yaml deployment.yaml kustomization.yaml service.yaml...