qiskit/.mergify.yml

---
pull_request_rules:
  - name: backport
    conditions:
      - label=stable backport potential
    actions:
      backport:
        branches:
          - stable/1.2
Stop using mergify merge queue feature (#9807) Due to recent changes in the mergify configuration/service the merge queue feature of mergify is no longer working as expected. It's not clear if this just a temporary bug in mergify, a longer term change in behavior (which requires all PR authors to be registered on mergify), or some incompatibility between the github api and mergify. However, because we're no longer able to rely on it we've moved to using github's native merge queue feature [1][2] instead. Since this new merge queue would conflict with mergify's this commit removes the merge queue configuration from the mergify configuration. The configuration for stable backporting is left in place because github doesn't natively offer that feature and it appears to still work fine. [1] https://github.blog/changelog/2023-02-08-pull-request-merge-queue-public-beta/ [2] https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue 2023-03-17 06:32:14 +08:00			`---`
Add mergify config (#3352) This commit adds a basic configuration for using mergify.io. It simply will just squash merge the PR if it's been approved and passes ci. The configuration documentation for the service can be found here: https://doc.mergify.io/configuration.html 2019-10-30 06:16:22 +08:00			`pull_request_rules:`
Add auto backport rule to mergify configuration (#4065) This commit adds a rule to the mergify configuration to automatically attempt to backport a PR with the stable backport potential label on it. If there is a merge conflict we'll still have to manually backport, but for cleanly applying backports this saves us the manual step of having to backport commits. The one caveat here is that we will have to remember to bump the stable branch number post release to the new branch, which means there are now 3 locations to update after a release instead of 2. 2020-04-03 04:06:58 +08:00			`- name: backport`
			`conditions:`
			`- label=stable backport potential`
			`actions:`
			`backport:`
			`branches:`
Bump main branch version post 1.2 branch (#12815) 2024-07-26 00:47:38 +08:00			`- stable/1.2`