Skip to content

test: scratch probe - does a GITHUB_TOKEN branch update trigger PR checks? - #3698

Closed
eleshar wants to merge 2 commits into
developfrom
ci/scratch-token-probe
Closed

test: scratch probe - does a GITHUB_TOKEN branch update trigger PR checks?#3698
eleshar wants to merge 2 commits into
developfrom
ci/scratch-token-probe

Merge branch 'develop' into ci/scratch-token-probe

30105ad
Select commit
Loading
Failed to load commit list.
Mergify / Summary succeeded Sep 30, 2026 in 1s

1 potential rule

Rule: Keep same-repository pull requests on develop current (update)

  • #commits-behind > 0
  • #commits-behind > 0 [📌 update requirement]
  • -closed [📌 update requirement]
  • -conflict
  • -conflict [📌 update requirement]
  • -draft
  • -from-fork
  • base=develop
  • queue-position = -1 [📌 update requirement]
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

View more details on Mergify