-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
merge queue: embarking release/current (f8b06df) and #9447 together #9484
Conversation
…omments-from-rom-user-are-allowed fix: Cannot comment when comments from rom user are allowed
fix: Fix/doc v3 customize setting
support(jsdoc): Add document to export.js
support(jsdoc): Add document to forgot-password.js
…-name fix: put / before the page name
…ng-export fix: TypeError occurs during export
|
❌ This pull request has failed checks. #9447 will be removed from the queue. ❌
Branch release/current (f8b06df) and #9447 are embarked together for merge.
This pull request has been created by Mergify to speculatively check the mergeability of #9447.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.
Required conditions of queue
default
for merge:-check-failure ~= test-prod-node20 /
-check-failure ~= ci-app-
-check-failure ~= ci-slackbot-
check-success = test-prod-node20 / build-prod
check-success = test-prod-node20 / launch-prod
check-success ~= ci-app-launch-dev
check-success ~= ci-app-lint
check-success ~= ci-app-test
check-success ~= test-prod-node20 / run-playwright
Required conditions to stay in the queue:
-check-failure ~= ci-app-
-check-failure ~= ci-slackbot-
-check-failure ~= test-prod-node20 /
check-success ~= ci-app-launch-dev
check-success ~= ci-app-lint
check-success ~= ci-app-test