You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
current behaviour if digger.yml is absent in a repo PR is that digger will try to automatically traverse folders and generate projects itself.
This behaviour should be changed to skip digger entirely and Noop, no comments left on PR. This is to avoid random failure messages appearing in a repo before it is actually setup
If a user wants digger to automatically discover and traverse projects the behaviour should be explicitly configured using generate_projects or others specified in a digger.yml
Applies to both backendless and orchestrator modes. Backendless job runs and Noops. Orchestrator: log something in backend and take no action in repo
Reported by NL
The text was updated successfully, but these errors were encountered:
current behaviour if digger.yml is absent in a repo PR is that digger will try to automatically traverse folders and generate projects itself.
This behaviour should be changed to skip digger entirely and Noop, no comments left on PR. This is to avoid random failure messages appearing in a repo before it is actually setup
If a user wants digger to automatically discover and traverse projects the behaviour should be explicitly configured using
generate_projects
or others specified in a digger.ymlApplies to both backendless and orchestrator modes. Backendless job runs and Noops. Orchestrator: log something in backend and take no action in repo
Reported by NL
The text was updated successfully, but these errors were encountered: