Horreum
Horreum copied to clipboard
Assign different actions to different Change detection algorithms
Describe the bug
Different change detection algorithms have their own strengths and weaknesses and can potentially be used for different purposes, e.g. thresholds for pass/fail, eDivisive for trends etc
The action each algorithm triggers could be different, i.e eDivisive -> email engineers threshold -> pass/fail action (GH issue)