fix: Move Documents load time and emit meaningful content timestamp #1460
Mergify / Summary
succeeded
Apr 22, 2024 in 1s
1 potential rule
Rule: Automatic strict merge (queue)
-
#approved-reviews-by>=1
-
label=ready-to-merge
-
status-success=Travis CI - Pull Request
- any of: [🔀 queue conditions]
- all of: [📌 queue conditions of queue
default
]-
#approved-reviews-by>=1
[🛡 GitHub branch protection] -
branch-protection-review-decision=APPROVED
[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-neutral=Travis CI - Pull Request
-
check-skipped=Travis CI - Pull Request
-
check-success=Travis CI - Pull Request
-
-
#changes-requested-reviews-by=0
[🛡 GitHub branch protection] - any of: [🛡 GitHub branch protection]
-
check-success=Summary
-
check-neutral=Summary
-
check-skipped=Summary
-
-
- all of: [📌 queue conditions of queue
-
#changes-requested-reviews-by=0
-
#review-requested=0
-
-draft
[📌 queue requirement] -
base=master
-
label!=do-not-merge
-
title~=^(build|ci|chore|docs|feat|fix|perf|refactor|revert|style|test)(\([^)]+\))?:\s.+$
- any of: [📌 queue -> configuration change requirements]
-
-mergify-configuration-changed
-
check-success=Configuration changed
-
💖 Mergify is proud to provide this service for free to open source projects.
🚀 You can help us by becoming a sponsor!
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branch
Additionally, on Mergify dashboard you can:
- look at your merge queues
- generate the Mergify configuration with the config editor.
Finally, you can contact us on https://mergify.com
Loading