docs(nx-cloud): ensure nx cloud statuses are not enforced on github (#30080)
<!-- Please make sure you have read the submission guidelines before posting an PR --> <!-- https://github.com/nrwl/nx/blob/master/CONTRIBUTING.md#-submitting-a-pr --> <!-- Please make sure that your commit message follows our format --> <!-- Example: `fix(nx): must begin with lowercase` --> <!-- If this is a particularly complex change or feature addition, you can request a dedicated Nx release for this pull request branch. Mention someone from the Nx team or the `@nrwl/nx-pipelines-reviewers` and they will confirm if the PR warrants its own release for testing purposes, and generate it for you if appropriate. --> ## Current Behavior <!-- This is the behavior we have today --> Since statuses are generated dynamically based off of commands executed, enforcing old statuses on Github will result in a "Waiting for status" message which can block in progress PRs. The recommendation is then to only enforce status checks on the default branch and not enforce any Nx Cloud related status checks. ## Expected Behavior <!-- This is the behavior we should expect with the changes in this PR --> ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #
This commit is contained in:
parent
f6404f57be
commit
377f5f6dfc
BIN
docs/nx-cloud/set-up/do-not-enforce-nx-cloud-status-checks.webp
Normal file
BIN
docs/nx-cloud/set-up/do-not-enforce-nx-cloud-status-checks.webp
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 122 KiB |
@ -63,3 +63,10 @@ Make sure [GitHub checks are enabled](https://circleci.com/docs/2.0/enable-check
|
||||
Ensure this step from the plugin instructions is followed:
|
||||
|
||||
Prerequisite: only GitHub App with proper permissions can publish checks, this guide helps you authenticate your Jenkins as a GitHub App.
|
||||
|
||||
## Github Status Checks
|
||||
|
||||
The Nx Cloud GitHub Integration updates your PR with commit statuses that reflect the real-time progress of your runs. These statuses are generated dynamically based on your running commands. Enforcing these dynamically-named checks within your branch protection rules is not recommended, as it can result in stuck checks displaying `Waiting for status to be reported`.
|
||||
|
||||
From your repository, go to `Settings -> Branches -> Protect matching branches` and ensure that no Nx Cloud status checks are listed in the `Require status checks to pass before merging` list. Enforcing that status checks pass on your default branch is sufficient.
|
||||

|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user