.github/workflows: Only run tool buildtests in merge queue

[AnnsAnns]

Contribution description

The build tests are taking a lot of CI time (also spam the CI status page) while I couldnt find a single instance where they actually failed, mostly because these tools are rarely ever touched. I tried properly filtering them to only trigger when something changes but the current design of these tests didn't make that trivial + it required changes to our current merge rules on github. This is a (hopefully working) compromise for now where this only gets triggered in the merge queue which should at least stop it from instantly doing stuff as soon as a PR gets opened which is a complete waste.

Testing procedure

idk, push, yolo

Issues/PRs references

Kinda relates to #22679 but mostly in a procrastination kind of way I guess

Declaration of AI-Tools / LLMs usage:

AI-Tools / LLMs that were used are:

• I looked for solutions with DeepSeek v4.1 Flash but even the LLM couldn't help me find a good solution :(

[riot-ci]

Murdock results

✔️ PASSED

4201227 .github/workflows: Only run buildtests in merge queue

Success	Failures	Total	Runtime
1	0	1	02m:29s

Artifacts

• Documentation preview

[AnnsAnns]

Ah these are pre-requirements to even get into the merge queue? :/

[crasbe]

Ah these are pre-requirements to even get into the merge queue? :/

That setting can be changed by an admin. Although you could modify the tools-build-success test to return success if the other tests were skipped due to the files not being changed.

Not sure what to do about the python-tests and whether or not that is also part of the tools-build-success consideration (i.e. the explicit requirement could be lifted for it).

[Teufelchen1]

Does merging of a merge group count as push to the master branch? 🤔 The github docs confuse me.

[Teufelchen1]

The build tests are taking a lot of CI time [..]

Do they? What do you consider "a lot of CI time"?

[crasbe]

The build tests are taking a lot of CI time [..]

Do they? What do you consider "a lot of CI time"?

The tools-buildtest workflow is the one that takes the most amount of time. I'm not sure if they also run on Murdock though?

[Teufelchen1]

I was looking for that statistic for 10 min and couldn't find it. Concluding I had misremembered. But of course it is under insight and not under actions or in the settings. 🫠

[Teufelchen1]

Okay, I agree it is using a lot of CI.
Also, shouldn't we run those kind of tests in murdock? Just to be less dependable on github.