measuring software's embodied carbon; was: online meetup Wed. 20 Nov. 18h UTC | Green Coding Solutions: "Eco-CI" and "Powerletrics"

[Sune Vuorela]

On 2024-11-29, Ben Cooksley <bcooksley at kde.org> wrote:
> We already have optimisation in place to prevent duplicate jobs triggering
> when a merge request already exists, but yes there is potentially some work
> to be done here to improve efficiency.
> If a developer knows they are going to be immediately creating a MR then
> they can use the Git option ci.skip to prevent CI from running (git push
> -o ci.skip)

I wonder if it is worth switching this around.

My pattern is at least creating MR right after a push. I don't know if
I'm the majority or minority here. 

/Sune