1,039 opted-in GitHub users rate their own code a small lever on emissions

A tool that measures the environmental impact of a code change has to get from what the repository can see to what the hardware and its power supply actually used. GitHub's post is explicit that runtime alone does not prove a reduction in energy use or emissions, and it lists what does affect the result: hardware, workload, location, time, and the source of electricity ^[14]. A pull request can characterise the workload. The other four belong to whoever provisioned the runner and to the hour the job ran.

That ordering shows up in what respondents asked for in their own words. They wanted help estimating the footprint of repositories and CI/CD workflows, finding unnecessary GitHub Actions runs, improving code efficiency, and comparing AI use with other sources of compute demand ^[13]. Counting redundant workflow runs can happen without a grid model. Reporting grams of CO2 per merge needs all five inputs ^[14].

The same respondents rate their own leverage low. Ten percent said the way they develop and write software has a large effect on reducing their personal environmental impact, 28% said moderate, and 63% said small ^[8]. Eighty percent expressed interest in efficiency tooling, eight times the 10% who claimed a large effect ^[18]. Thirty-eight percent put the effect at moderate or large ^[19].

GitHub frames the finding as a shortfall in tooling: developers know efficient software matters, but many lack a clear way to find waste, measure an improvement, and make the case for fixing it ^[15]. "The gap is not interest. It's a practical path to action," the post says ^[22]. The items reported measure interest, and the post does not say whether respondents had tried a measurement tool and given up.

For the 80% to describe an engineering organisation, that organisation would have to look like this panel. On five questions that also appear in Yale's nationally representative Climate Change in the American Mind survey, the GitHub respondents came in higher than US adults every time, including 86% against 68% that global warming is happening and 68% against 45% that it will harm them personally at least a moderate amount ^[12]. The second is a 23-point gap, the widest of the five ^[21]. GitHub says the results describe survey respondents and should not be treated as representative of every developer or GitHub user, because the sample came from users who had opted in to marketing communications ^[3].

The loop the post suggests is to identify unnecessary compute, propose a change, test it, and let maintainers decide what ships ^[16]. It also lists the reasons such a change passes review with no climate argument attached: lower infrastructure costs, better performance, reduced latency, freed capacity ^[17]. Several respondents warned against making environmental claims without evidence ^[13].