When implementing status check, for subsequent following dev iterations, if a file change occurs the previous context in which status check runs got canceled.
I had verified this on the prototype branch
The reason for this is,
status check shares the same context as current dev iteration context.
when a change is triggered, we cancel the previous context which should cause status check to interrupt.
dgageot
commented
4 years ago
When implementing status check, for subsequent following dev iterations, if a file change occurs the previous context in which status check runs got canceled. I had verified this on the prototype branch
The reason for this is,
Verify if we still do this.