Travis Carden

Oh, maybe I should've been explicit in my reasoning for filing this (and other) issues in our queue: I know that Starshot didn't create them and probably won't be where...

See https://github.com/phenaproxima/starshot-prototype/issues/106#issuecomment-2183223336. I created this issue as a placeholder for filing and tracking just such an issue in Gin. 🙂

[Per the maintainer:](https://www.drupal.org/project/pathauto/issues/3455144#comment-15651112) > a 2.x release will then remove it, but I have no plans to create that any time soon and I won't do it only for that....

It's just to prevent you from accidentally overwriting an existing application, causing corruption or data loss. I think it's a firm requirement. However, since you apparently know what you're doing,...

Oops; I meant to say `commit`, not `stage`. Since you already have a staging directory, you don't need to `begin` anymore--that's effectively already been done. What you're doing now from...

> the first `commit` switches the active and staging directories, right? It syncs them, if that's what you mean. In simple terms, the first `commit`--from staging to active--will update and...

It seems like my initial proposal exposes you to too many unintended consequences from semantic misalignment. What if you [override the service](https://symfony.com/doc/current/service_container/service_decoration.html) instead? It would look something like this: ```yaml...