From: lucas@debian.org 
  
 On 25/08/25 at 13:43 -0700, Otto Kek€l€inen wrote: 
 > Hi, 
 > 
 > > On 24/08/25 at 12:18 -0700, Otto Kek€l€inen wrote: 
 > ... 
 > > > I just noticed one developer pushed git commits to 493 different 
 > > > packages in Salsa, triggering hundreds of Salsa CI pipelines. 
 > > 
 > > I think that was me (during adding debian/gbp.conf files to many 
 > > packages, during DEP-14 migration). 
 > 
 > Could you perhaps limit your updates to maybe max 100 commits per day? 
  
 Err, that would be extremely impractical :) 
 I'm surprised that Salsa CI cannot handle that load. I saw that Salsa 
 got a major upgrade yesterday evening, maybe there's a regression 
 somewhere? 
  
 Anyway, I cancelled all pipelines that were started by my changes, let's 
 see if it improves things. 
  
 > I suspect this is blocking a lot of other people from doing the 
 > development and uploads they were planning to do. 
 > 
 > ... 
 > > > If you know you are doing a minor typofix, removing a trailing space 
 > > > etc and don't need CI at all, please pass the git option `-o ci.skip` 
 > > > when pushing. 
 > > > 
 > > > Example: 
 > > > git push -o ci.skip 
 > > 
 > > I'm using the GitLab REST API through python-gitlab to automate those 
 > > commits. Do you know if there's a way to do the same thing in that case, 
 > > other that using "[skip ci]" in the commit message, which pollutes the 
 > > git history? 
 > 
 > Indeed, it seems to be the case that the API does not offer to pass 
 > git options. I added my vote in 
 > https://gitlab.com/gitlab-org/gitlab/-/issues/26422 now. Maybe if you 
 > add your "user story" they might have more interest in implementing 
 > it. 
  
 Note that it my case, some pipelines were triggered by adding/changing 
 debian/gbp.conf, but others were triggered by branch renames. So even 
 using a custom commit message would not work. 
  
 Lucas 
  
 --- SoupGate-Win32 v1.05 
  * Origin: you cannot sedate... all the things you hate (1:229/2)