From: noisycoil@disroot.org 
  
 On 15/08/25 18:34, Raphael Hertzog wrote: 
 > Hi, 
 > 
 > On Fri, 15 Aug 2025, NoisyCoil wrote: 
 >> Since uploading is considered an optional task, shouldn't the workflow be 
 >> considered completed without it being executed? Or shouldn't this be 
 >> configurable at least? 
 > When you start a workflow, you can pass parameters to the workflow. In 
 > the case of the `debian_pipeline` workflow [1], it supports an 
 `enable_upload` 
 > parameter... and for the `upload-to-unstable` workflow template, we set it 
 to 
 > True since the goal is to upload. 
 This is not quite what I had in mind. When manual intervention is 
 required (such as when uploading), it is quite common for a workflow to 
 be considered completed regardless of whether that intervention has 
 happened or not. For instance, this is the default in gitlab (hence 
 salsa) pipelines with manual jobs: gitlab pipelines are considered 
 passing (and completed) even if the manual jobs where not run, unless 
 otherwise configured. But deciding where to draw the line between what's 
 completed and what's not can be quite subjective, so it's not a hill I'm 
 willing to die on :-) 
  
 Very much looking forward to testing Debusine! 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)