From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

At that place it is simply a no-op.
It is an action that is triggered after the settings script is evaluated.
But this event is long passed.

But if you for example have an init script and do it there,
then you could for example manipulate the repositories or validate that no bad ones are there or similar things.

Thanks, that's not what the docs say, so I guess it's another bug. I'll make an issue.

It says:
&gt; Adds an action to be called when the build settings have been loaded and evaluated. The settings object is fully configured and is ready to use to load the build projects.
This can be interpreted as exactly what I said. :slightly_smiling_face:
If you add such an action in a build script, the "ready to load the build projects" is not really true, as the projects are already loaded. :slightly_smiling_face:

But it could maybe be written a bit clearer, that this is only effective if called from an init or settings script.

In a settings script it practically is like `afterEvaluate` for build scripts

well, it's called `settingsEvaluated {}`, not `settingsEvaluatedUnlessAlreadyEvaluated {}`