[chore] Mark "scoped-test" CI workflow as "required"

[pjanotti]

Per SIG meeting on 05/13/2025:

Opening an issue to give visibility for the ask of making the scoped-test CI workflow as required on CI. This workflow has proved very useful in avoiding merges breaking Windows builds and has being stable for some time. This workflow only runs when there are changes to go source files.

cc @open-telemetry/collector-contrib-approvers

[mx-psi]

I support doing this

[dmitryax]

Made the scoped-tests required job

[crobert-1]

I've got a PR stuck with the status:

scoped-tests Expected — Waiting for status to be reported.

However, the test run itself is successful if you browse to the scoped-test workflow results in GitHub. I'm seeing this in other PRs too.

This check is shown as successful in the list of checks:

scoped-test / scoped-tests (windows-latest) (pull_request)

This check is shown as required:

scoped-tests

@dmitryax Do you happen to have any more context here? Maybe we just have the wrong name for a required check? (I've seen this has happened for others before)

EDIT: I'm not sure which name we should use, but the actual workflow's name is scoped-test, so maybe it should just be scoped-test instead of scoped-tests.

[dmitryax]

I'm not sure which name we should use, but the actual workflow's name is scoped-test, so maybe it should just be scoped-test instead of scoped-tests.

It should be job name, not workflow.

Probably because the job has a matrix in it. We either need to remove the matrix or set the required test to scoped-tests (windows-latest)

I'm actually concerned that the job has if condition. We might run into the same issue if the condition isn't met

[crobert-1]

Confirming this change was successful after rebasing, my PR shows the required job as successful. Thanks @dmitryax!