Add license scan report and status #235
Open
Mergify / Summary
succeeded
Aug 1, 2025 in 2s
1 potential rule
Rule: Approved PRs (merge)
-
approved-reviews-by=binhonglee -
status-success=ci/circleci: core-v2.2.0 -
status-success=ci/circleci: core-vstable -
status-success=ci/circleci: tsutil -
status-success=core (2.2.0) -
status-success=core (stable) -
status-success=coverage -
status-success=documentation -
status-success=security/snyk (binhonglee) -
status-success=tsutil -
-closed[📌 merge requirement] -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
1 not applicable rule
Rule: Dependabot updates (merge)
-
author~=^dependabot(|-preview)\[bot\]$ -
status-success=ci/circleci: core-v2.2.0 -
status-success=ci/circleci: core-vstable -
status-success=ci/circleci: tsutil -
status-success=codecov/patch -
status-success=codecov/project -
status-success=core (2.2.0) -
status-success=core (stable) -
status-success=coverage -
status-success=documentation -
status-success=security/snyk (binhonglee) -
status-success=tsutil -
-closed[📌 merge requirement] -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] - any of: [📌 merge -> configuration change requirements]
-
-mergify-configuration-changed -
check-success = Configuration changed
-
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 refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill 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