Can someone explain this error on PR?

[deeluxe74]

Summary

Hi,

I try to start contributing. Sorry if my question is trivial 😅
I have opened a PR here #74803, someone have set a tag and a message (that I don't quite understand).

But my main problem is from this tag, I get this following error:

Set up runner

A job started hook has been configured by the self-hosted runner administrator
Run '/root/validate-job.sh'
Validating job...
PR labels: [
  {
    id: 19656[2](https://github.com/vercel/next.js/actions/runs/12735528371/job/35494398457?pr=74803#step:2:2)5097,
    node_id: 'MDU6TGFiZWwxOTY1NjI1MDk3',
    url: 'https://api.github.com/repos/vercel/next.js/labels/type:%20next',
    name: 'type: next',
    color: 'f6aff7',
    default: false,
    description: ''
  }
]
posting comment https://api.github.com/repos/vercel/next.js/issues/7[4](https://github.com/vercel/next.js/actions/runs/12735528371/job/35494398457?pr=74803#step:2:5)803/comments
Job unable able to validate for deeluxe[7](https://github.com/vercel/next.js/actions/runs/12735528371/job/35494398457?pr=74803#step:2:8)4 on PR https://github.com/vercel/next.js/pull/74[8](https://github.com/vercel/next.js/actions/runs/12735528371/job/35494398457?pr=74803#step:2:9)03
Error: Process completed with exit code 1.

Thanks for your time

Additional information

No response

Example

No response

[icyJoseph]

Since Next.js is a popular framework, many people send PR's, and while that's nice, it also means that CI jobs would trigger on every new PR, which consumes resources, might make other PR CI jobs slower, etc, you know, there is a queue of jobs, and just about enough memory to allow them to go. One could submit a PR that blocks CI for a while, and then that agent would be unusable until a timeout or something...

So, to avoid that, a core maintainer has to come into your PR, and allow CI by clicking the checkbox. Until the core maintainer gives it a go, the PR CI jobs will be dormant.