if everything requires same args, dose it still need to be extra_test_args?

it's repeated multiple times, I think this is the easiest way to manage it for now.

we repeat this arg in 2/3 times that we run the test suite. I can "hardcode" it in all other places instead, not a big deal

extra_test_args changes the test name. then merge queue settings also must be updated.
that's not a big deal when it occasionally changes. but it happens more than common these days. So i wish that's still an argument, but not being a part of job title.

also it makes the CI job name unnecessary longer, not a big deal itself too though.

extra_test_args changes the test name. then merge queue settings also must be updated. that's not a big deal when it occasionally changes. but it happens more than common these days. So i wish that's still an argument, but not being a part of job title.

also it makes the CI job name unnecessary longer, not a big deal itself too though.

CPython uses an external file to manage their CI commands, we could do the same using just for example.

bevy wrote their own tool for that, we could do something similar.

I'm in favor of starting with the just approach (or similar), if you think it's a good idea.

There's another option which I'm less of a fan of, but still worth mentioning. cargo alias can also do that, but that's adding another layer without the full features that justgives us, i.e. reuse of variables. (we can't define a variable called common_args and use it everywhere).

lmk if that makes sense to you and/or worth implementing

either way i am good as long as contributors still can copy the same CI command from web CI view to their terminal