Skip to content
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

CMake: Don't force users to build specific library type #15526

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

CMake: Don't force users to build specific library type

d2c9101
Select commit
Loading
Failed to load commit list.
Open

CMake: Don't force users to build specific library type #15526

CMake: Don't force users to build specific library type
d2c9101
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Oct 31, 2024 in 2s

1 rule matches and 13 potential rules

Rule: label needs: work when changes were requested (label)

  • #changes-requested-reviews-by>0

Rule: label needs: work when GitHub Actions jobs have failed (label)

  • check-failure=cmake-checks
  • check-failure=docs-check
  • check-failure=frozen-tools-check
  • check-failure=include-check
  • check-failure=license-check
  • check-failure=pin-validation
  • check-failure=python-tests
  • check-failure=style-check
  • label!='needs: work'
  • label!=mergify skip

Rule: label needs: work when Jenkins CI failed - pr head (label)

  • check-failure~=continuous-integration/jenkins/pr-head
  • label=needs: CI
  • -closed
  • label!=mergify skip

Rule: label needs: work when Jenkins CI failed - any of the pipeline (label)

  • check-failure~=^jenkins-ci
  • label=needs: CI
  • label!=mergify skip

Rule: label needs: CI when at least one reviewers approval (label)

  • #approved-reviews-by>=1
  • check-success=cmake-checks
  • check-success=docs-check
  • check-success=frozen-tools-check
  • check-success=include-check
  • check-success=license-check
  • check-success=pin-validation
  • check-success=python-tests
  • check-success=style-check
  • #changes-requested-reviews-by=0
  • -check-failure~=continuous-integration/jenkins/pr-head
  • -check-success~=continuous-integration/jenkins/pr-head
  • -conflict
  • label!=needs: preceding PR

✅ Rule: remove outdated reviews (dismiss_reviews)

Rule: label needs: work when there is a conflict (comment, label)

  • conflict
  • -closed

Rule: label "ready for merge" when ready (label)

  • #approved-reviews-by>=1
  • check-success=cmake-checks
  • check-success=docs-check
  • check-success=frozen-tools-check
  • check-success=include-check
  • check-success=license-check
  • check-success=pin-validation
  • check-success=python-tests
  • check-success=style-check
  • check-success~=continuous-integration/jenkins/pr-head
  • label=needs: CI
  • #changes-requested-reviews-by=0
  • -check-failure~=^jenkins-ci
  • label!=do not merge
  • label!=mergify skip

Rule: remove ready for merge when merged (label)

  • label=ready for merge
  • merged

Rule: add "do not merge" label when WIP is in title (label)

  • title~=^(\[wip\]( |:) |\[WIP\]( |:) |wip( |:) |WIP( |:)).*

Rule: release version is a must for merged PRs part 1 (comment, label)

  • merged
  • -label~=^(Release review required)
  • -label~=^(release-type)
  • -label~=^(release-version)

Rule: release version is a must for merged PRs part 2.1 (label)

  • label=^(release-version)
  • merged

Rule: release version is a must for merged PRs part 2.2 (label)

  • label=^(release-type)
  • merged

Rule: remove release version and needs labels (label)

  • closed
  • -merged

💖  Mergify is proud to provide this service for free to open source projects.

🚀  You can help us by becoming a sponsor!


2 not applicable rules

Rule: add label feature branch for feature branch additions (label)

  • base~=^feature

Rule: add release review required to release branches (label)

  • base~=^mbed-os-5.15
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