Av1an/.mergify.yml

pull_request_rules:
  - name: automatic squash-merge for master when CI passes and approved
    conditions:
      - "#approved-reviews-by>=1"
      - and:
          # Unfortunately, we cannot just say "all CI must pass".
          # This is not a bot limitation, but a limitation in Github itself.
          - check-success=all-tests
          - check-success=docker
          - check-success=SonarCloud Code Analysis
      - base=master
    actions:
      queue:
        name: default
        method: squash
        update_method: rebase
  - name: automatic merge for stable when CI passes and approved
    conditions:
      - "#approved-reviews-by>=1"
      - and:
          # Unfortunately, we cannot just say "all CI must pass".
          # This is not a bot limitation, but a limitation in Github itself.
          - check-success=all-tests
          - check-success=docker
          - check-success=SonarCloud Code Analysis
      - base=stable
    actions:
      queue:
        name: default
        method: rebase
        update_method: rebase

queue_rules:
  - name: default
    conditions:
      - and:
          # Unfortunately, we cannot just say "all CI must pass".
          # This is not a bot limitation, but a limitation in Github itself.
          - check-success=all-tests
          - check-success=docker
          - check-success=SonarCloud Code Analysis
Add mergify config (#445) * Add mergify config This config includes the following rules: - Automatically merge once a PR passes all tests and is approved. - Automatically backport each PR from our main branch into our stable branch * Merge all tests into one run * Cleanup and speed up test suite * Migrate to a docker image with dav1d * Create CI profile with debug assertions enabled * Use faster params for all encoders Co-authored-by: Redzic <yusufredzic@gmail.com> 2021-12-15 22:58:00 +00:00			`pull_request_rules:`
Do not automatically backport each PR to stable The way we have been doing releases does not coincide well with how we have been utilizing our stable branch. Given that we release from master, and that many people in the community use master on a daily basis, it makes more sense for stable to always match the latest released version, and for master to include unreleased changes which are considered "stable". For experiments, we should instead use a feature branch per experiment until we are confident that it is ready to be merged into master. 2022-01-18 23:30:47 +00:00			`- name: automatic squash-merge for master when CI passes and approved`
Add mergify config (#445) * Add mergify config This config includes the following rules: - Automatically merge once a PR passes all tests and is approved. - Automatically backport each PR from our main branch into our stable branch * Merge all tests into one run * Cleanup and speed up test suite * Migrate to a docker image with dav1d * Create CI profile with debug assertions enabled * Use faster params for all encoders Co-authored-by: Redzic <yusufredzic@gmail.com> 2021-12-15 22:58:00 +00:00			`conditions:`
			`- "#approved-reviews-by>=1"`
Always run CI so that we can merge all PRs 2022-01-03 21:35:09 +00:00			`- and:`
Auto-merge if no tests were run because only config files modified 2021-12-16 14:06:52 +00:00			`# Unfortunately, we cannot just say "all CI must pass".`
			`# This is not a bot limitation, but a limitation in Github itself.`
Always run CI so that we can merge all PRs 2022-01-03 21:35:09 +00:00			`- check-success=all-tests`
			`- check-success=docker`
			`- check-success=SonarCloud Code Analysis`
Add mergify config (#445) * Add mergify config This config includes the following rules: - Automatically merge once a PR passes all tests and is approved. - Automatically backport each PR from our main branch into our stable branch * Merge all tests into one run * Cleanup and speed up test suite * Migrate to a docker image with dav1d * Create CI profile with debug assertions enabled * Use faster params for all encoders Co-authored-by: Redzic <yusufredzic@gmail.com> 2021-12-15 22:58:00 +00:00			`- base=master`
			`actions:`
Additional changes for mergify - Remove usage of deprecated "strict" param by using queues - Add auto merge for stable backports - Fix assignees for stable patches 2021-12-15 23:21:33 +00:00			`queue:`
			`name: default`
Add mergify config (#445) * Add mergify config This config includes the following rules: - Automatically merge once a PR passes all tests and is approved. - Automatically backport each PR from our main branch into our stable branch * Merge all tests into one run * Cleanup and speed up test suite * Migrate to a docker image with dav1d * Create CI profile with debug assertions enabled * Use faster params for all encoders Co-authored-by: Redzic <yusufredzic@gmail.com> 2021-12-15 22:58:00 +00:00			`method: squash`
Additional changes for mergify - Remove usage of deprecated "strict" param by using queues - Add auto merge for stable backports - Fix assignees for stable patches 2021-12-15 23:21:33 +00:00			`update_method: rebase`
Do not automatically backport each PR to stable The way we have been doing releases does not coincide well with how we have been utilizing our stable branch. Given that we release from master, and that many people in the community use master on a daily basis, it makes more sense for stable to always match the latest released version, and for master to include unreleased changes which are considered "stable". For experiments, we should instead use a feature branch per experiment until we are confident that it is ready to be merged into master. 2022-01-18 23:30:47 +00:00			`- name: automatic merge for stable when CI passes and approved`
Additional changes for mergify - Remove usage of deprecated "strict" param by using queues - Add auto merge for stable backports - Fix assignees for stable patches 2021-12-15 23:21:33 +00:00			`conditions:`
Do not automatically backport each PR to stable The way we have been doing releases does not coincide well with how we have been utilizing our stable branch. Given that we release from master, and that many people in the community use master on a daily basis, it makes more sense for stable to always match the latest released version, and for master to include unreleased changes which are considered "stable". For experiments, we should instead use a feature branch per experiment until we are confident that it is ready to be merged into master. 2022-01-18 23:30:47 +00:00			`- "#approved-reviews-by>=1"`
Always run CI so that we can merge all PRs 2022-01-03 21:35:09 +00:00			`- and:`
			`# Unfortunately, we cannot just say "all CI must pass".`
			`# This is not a bot limitation, but a limitation in Github itself.`
			`- check-success=all-tests`
			`- check-success=docker`
			`- check-success=SonarCloud Code Analysis`
Additional changes for mergify - Remove usage of deprecated "strict" param by using queues - Add auto merge for stable backports - Fix assignees for stable patches 2021-12-15 23:21:33 +00:00			`- base=stable`
			`actions:`
			`queue:`
Avoid premium feature 2021-12-16 01:06:06 +00:00			`name: default`
Additional changes for mergify - Remove usage of deprecated "strict" param by using queues - Add auto merge for stable backports - Fix assignees for stable patches 2021-12-15 23:21:33 +00:00			`method: rebase`
			`update_method: rebase`

			`queue_rules:`
			`- name: default`
			`conditions:`
Always run CI so that we can merge all PRs 2022-01-03 21:35:09 +00:00			`- and:`
			`# Unfortunately, we cannot just say "all CI must pass".`
			`# This is not a bot limitation, but a limitation in Github itself.`
			`- check-success=all-tests`
			`- check-success=docker`
			`- check-success=SonarCloud Code Analysis`