docs: add quick start guide and glossary from learning-fromager repo #898
+88
−0
Mergify / Summary
succeeded
Dec 23, 2025 in 1s
3 potential rules
Rule: Add CI label (label)
- any of:
-
files~=.github/ -
files~=.markdownlint-config.yaml -
files~=e2e/ -
files~=pyproject.toml -
files~=tests/ -
title~=^ci: -
title~=^e2e: -
title~=^hatch:
-
Rule: Add Mergify label (label)
- any of:
-
files~=.mergify.yml$ -
title~=^mergify:
-
Rule: Automatic merge on approval (merge)
- all of:
- all of:
-
#approved-reviews-by>=1
-
-
-draft -
check-success=e2e (3.11, 1.75, ci_bootstrap_parallel_suite, ubuntu-latest) -
check-success=e2e (3.11, 1.75, ci_bootstrap_suite, ubuntu-latest) -
check-success=e2e (3.11, 1.75, ci_build_suite, ubuntu-latest) -
check-success=e2e (3.11, 1.75, ci_config_suite, ubuntu-latest) -
check-success=e2e (3.11, 1.75, ci_specialized_suite, ubuntu-latest) -
check-success=e2e (3.11, 1.75, ci_workflow_suite, ubuntu-latest) -
check-success=e2e (3.12, 1.75, ci_bootstrap_parallel_suite, ubuntu-latest) -
check-success=e2e (3.12, 1.75, ci_bootstrap_suite, ubuntu-latest) -
check-success=e2e (3.12, 1.75, ci_build_suite, ubuntu-latest) -
check-success=e2e (3.12, 1.75, ci_config_suite, ubuntu-latest) -
check-success=e2e (3.12, 1.75, ci_specialized_suite, ubuntu-latest) -
check-success=e2e (3.12, 1.75, ci_workflow_suite, ubuntu-latest) -
check-success=e2e (3.13, 1.75, ci_bootstrap_parallel_suite, ubuntu-latest) -
check-success=e2e (3.13, 1.75, ci_bootstrap_suite, ubuntu-latest) -
check-success=e2e (3.13, 1.75, ci_build_suite, ubuntu-latest) -
check-success=e2e (3.13, 1.75, ci_config_suite, ubuntu-latest) -
check-success=e2e (3.13, 1.75, ci_specialized_suite, ubuntu-latest) -
check-success=e2e (3.13, 1.75, ci_workflow_suite, ubuntu-latest) -
check-success=e2e (3.14, 1.75, ci_bootstrap_parallel_suite, macos-latest) -
check-success=e2e (3.14, 1.75, ci_bootstrap_parallel_suite, ubuntu-latest) -
check-success=e2e (3.14, 1.75, ci_bootstrap_suite, macos-latest) -
check-success=e2e (3.14, 1.75, ci_bootstrap_suite, ubuntu-latest) -
check-success=e2e (3.14, 1.75, ci_build_suite, macos-latest) -
check-success=e2e (3.14, 1.75, ci_build_suite, ubuntu-latest) -
check-success=e2e (3.14, 1.75, ci_config_suite, macos-latest) -
check-success=e2e (3.14, 1.75, ci_config_suite, ubuntu-latest) -
check-success=e2e (3.14, 1.75, ci_specialized_suite, macos-latest) -
check-success=e2e (3.14, 1.75, ci_specialized_suite, ubuntu-latest) -
check-success=e2e (3.14, 1.75, ci_workflow_suite, macos-latest) -
check-success=e2e (3.14, 1.75, ci_workflow_suite, ubuntu-latest) -
check-success=mypy -
check-success=unit (3.11, 1.75, macos-latest) -
check-success=unit (3.11, 1.75, ubuntu-latest) -
check-success=unit (3.12, 1.75, macos-latest) -
check-success=unit (3.12, 1.75, ubuntu-latest) -
check-success=unit (3.13, 1.75, macos-latest) -
check-success=unit (3.13, 1.75, ubuntu-latest) -
check-success=unit (3.14, 1.75, macos-latest) -
check-success=unit (3.14, 1.75, ubuntu-latest)
- all of:
-
-closed[📌 merge requirement] -
-conflict[📌 merge requirement] -
-draft[📌 merge requirement] - any of: [📌 merge -> 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 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