Skip to content

Merge branch 'main' into juniedoc-vm_0.5

d357ae3
Select commit
Loading
Failed to load commit list.
Merged

Add Junie/Gemini generated XML doc headers to half of the ViewModels. #3251

Merge branch 'main' into juniedoc-vm_0.5
d357ae3
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Dec 8, 2025 in 0s

1 potential rule

Rule: automatic merge for pull request based on label and ci success (merge)

  • -closed [📌 merge requirement]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • check-success=continuous-integration/appveyor/pr
  • label~=LGTM$
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

3 not applicable rules

Rule: automatic merge for Dependabot pull requests based on ci success (merge)

  • -closed [📌 merge requirement]
  • author=dependabot[bot]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • check-success=continuous-integration/appveyor/pr
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: automatic merge for Transifex pull requests based on ci success (merge)

  • -closed [📌 merge requirement]
  • author=transifex-integration[bot]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • check-success=continuous-integration/appveyor/pr
  • any of: [📌 merge -> configuration change requirements]
    • -mergify-configuration-changed
    • check-success = Configuration changed

Rule: automatic merge for ImgBot pull requests based on ci success (merge)

  • -closed [📌 merge requirement]
  • author=imgbot[bot]
  • -conflict [📌 merge requirement]
  • -draft [📌 merge requirement]
  • check-success=continuous-integration/appveyor/pr
  • 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 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