@stevhliu I’ve created a new pull request and hope to avoid any CircleCI errors this time.

@LysandreJik or @ydshieh, would you happen to know why the other two tests aren't being run?

Given the changes only affect docs, I believe we can safely ignore the circle ci docs @stevhliu

@stevhliu Who will merge the pull request ?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Given the changes only affect docs, I believe we can safely ignore the circle ci docs

Unfortunately, I can't merge it because the required tests aren't passing @LysandreJik :(

Merged 🚀

For the recorder

The CI is running under akkefa personal account. Please follow https://support.circleci.com/hc/en-us/articles/360008097173-Troubleshooting-why-pull-requests-are-not-triggering-jobs-on-my-organization- to fix it.

If you're following the fork instead of the upstream repo

A user who submits a pull request to your repository from a fork, but no pipeline is triggered with the pull request. This can happen when the user is following the project fork on their personal account rather than the project itself on CircleCI.

This will cause the jobs to trigger under the user's personal account. If the user is following a fork of the repository on CircleCI, we will only build on that fork and not the parent, so the parent’s PR will not get status updates.

In these cases, the user unfollows their fork of the project on CircleCI. This will trigger their jobs to run under the organization when they submit pull requests. Those users can optionally follow the source project if they wish to see the pipelines.