Commit 6851b8d
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -540,6 +540,13 @@ specific details of how to do this are included in the new collaborator | |||
| 540 | 540 | test run for you as approvals for the pull request come in. | |
| 541 | 541 | If not, you can ask a collaborator or triager to start a CI run. | |
| 542 | 542 | ||
| 543 | + CI access is only available to collaborators and members of the platform | ||
| 544 | + teams. If you are not yet in one of those teams then you will need someone | ||
| 545 | + to relay the results to you. If a CI has been completed and failed and a | ||
| 546 | + day or so has passed, it will be worth commenting in the issue to say you | ||
| 547 | + cannot see what failed and to politely request in the PR that someone gives | ||
| 548 | + you that information. | ||
| 549 | + | ||
| 543 | 550 | Ideally, the code change will pass ("be green") on all platform configurations | |
| 544 | 551 | supported by Node.js. This means that all tests pass and there are no linting | |
| 545 | 552 | errors. In reality, however, it is not uncommon for the CI infrastructure itself | |
0 commit comments