3 ms·

It used 1.8 days of time to run for a single day? I'm less curious about who's paying for it than who's _using _ it on your repo, because I can't even imagine h

• heelix 1y ago
  Not the OP, but a poorly behaving repo can turn and burn for six hours on every PR, rather than the handful of minutes one would expect. It happens - but usually that sort of thing should be spotted and fixed. More often then not, something is trying to pull artifacts and timing out rather than it being a giant monorepo.
• monster_truck 1y ago
  Have you looked at the default configuration? It runs any time there is a push to main.
  • saghm 1y ago
    2600 minutes still seems pretty high to me; even if every run took 10 minutes, that's 260 pushes! Even the busiest projects I've worked on have never merged triple-digit numbers of changes in a single day. It's hard for me to imagine seeing that level of activity outside of something like a monorepo with a lot of different projects in it or something with a huge number of external contributors, and I wouldn't have any expectation that the default configuration would make sense for me if I were managing a repo like that. Maybe I've just worked on smaller projects than the average developer, or I've just been in charge of creating new CI actions infrequently enough to be paranoid about what exactly would be happening, but I wouldn't even consider enabling something on a repo with that much traffic before spending a lot of time looking at the configurations.