Igor Zalutski

Closing because it's supported: https://docs.digger.dev/howto/apply-on-merge

Great idea @norman-zon, thanks for contributing! One important detail however: `google-lock-bucket` is unrelated to the state backend; it is used purely to store PR-level locks to achieve Atlantis-like workflow (preventing...

Similar concern (more like, confusion) came up in a prospective customer conversation (P.K.) - they had a long-lived PR and assumed that only the projects affected by the latest commit...

Issue creation added in #1239 Keeping this open for now because we'd also need to add updating and closing logic

There is at least one other user who didn't want to use Gitlab's (not Github's) artifact storage for plan files, citing security reasons. I would love to better understand this...

Related to #808

Potential solutions: - https://github.com/diggerhq/digger/issues/1107

Additional feedback from Francois (NT): "all projects are triggered if modules change, even though changes in certain modules aren't affecting certain projects".

### Idea for using git as a store for dependencies / TFVars In digger.yml, each project can define `exports` and `imports` lists, like this: ``` projects: - name: projA dir:...

More user feedback (M. U. 13.02.2024): _is there a way to handle dependant projects where plans for the second project wait until applies are done on the first project? i...