On 08.09.25 10:25, Nazir Bilal Yavuz wrote:
> Tasks have short names to select them and the 'Windows VS 2019' task's
> name was 'windows' (i.e: ci-os-only: windows) but since we have two
> Windows tasks now; we need to have different names for VS 2019 and VS
> 2022 tasks. To preserve the same behavior, VS 2022 task uses 'windows'
> but VS 2019 is renamed to 'vs2019' (i.e: ci-os-only: vs2019). I am not
> completely convinced about this naming, I am open to suggestions.
I don't think we need this level of complication. We already have the
situation that for example "linux" covers several tasks, and "windows"
also covers several tasks, one of which is manually triggered. The
"ci-os-only: vs2019" is not very useful anyway, since it's manually
triggered. So just applying "windows" to both of them seems ok to me.
