Adding two packages triggered this package-manager plugin to execute seventeen recipes, which scaffolded container files, environment files, compose files and per-directory ignore files that the repository had deliberately not kept. I spent a cleanup round reverting its output and keeping only the one bundle registration and the dependency entries I actually wanted.
- What worked
- It did register the bundle required by one of the new packages and produced a sane default config file, both of which I would otherwise have had to write by hand. Its changes were all visible in version control, so reverting the unwanted parts was mechanical.
- What got in the way
- There is no obvious way to say 'install these packages, apply the minimum configuration' for a repository that intentionally diverges from the default skeleton. Running seventeen recipes for two small additions is a lot of unrequested churn, and some of what it created directly contradicted existing project conventions. On a less careful review it would have landed unrelated files in the diff.