Add mergify configuration

[okurz]

No description provided.

[Martchus]

Looks like zypper crashes due to an unhandled C++ exception:

terminate called after throwing an instance of 'std::system_error'
  what():  Operation not permitted

I suppose this could be considered a zypper bug.

[okurz]

No, it's https://bugzilla.opensuse.org/show_bug.cgi?id=1190670 . Fixed in 3ae3006

[okurz]

meh, "Package 'python3-black' not found." in Leap 15.3

[Martchus]

Right, I only added it recently to devel:openQA:Leap:15.3 but that's of course not helping here. We needed a container with our devel repo enabled, maybe just reuse the openQA CI container?

[okurz]

to be fixed in #142

[okurz]

Rebased, refreshed, updated, verified. All ready for review now.

[foursixnine]

Change the approval requirement to members of @os-autoinst/asset-sync-and-integration

[okurz]

Change the approval requirement to members of @os-autoinst/asset-sync-and-integration

I don't think that's possible according to https://docs.mergify.com/workflow/actions/merge/ . Also I don't think that we need to overcomplicate things. Still only approvals from priviledged members of the organisation count, not like anybody

[foursixnine]

Change the approval requirement to members of @os-autoinst/asset-sync-and-integration

I don't think that's possible according to https://docs.mergify.com/workflow/actions/merge/ . Also I don't think that we need to overcomplicate things. Still only approvals from priviledged members of the organisation count, not like anybody

Not convinced. Ever heard of bad actors and account takeover? - If others (non members of @os-autoinst/tools-team) agree, and number of approvals is increased to 2 and I can reconsider.

I am not a fan of automated merges on things that go live - also no description is provided nor reasoning as to why is it important for this repository.

[okurz]

Change the approval requirement to members of @os-autoinst/asset-sync-and-integration

I don't think that's possible according to https://docs.mergify.com/workflow/actions/merge/ . Also I don't think that we need to overcomplicate things. Still only approvals from priviledged members of the organisation count, not like anybody

Not convinced. Ever heard of bad actors and account takeover? - If others (non members of @os-autoinst/tools-team) agree, and number of approvals is increased to 2 and I can reconsider.

Sure, let's play it safe(r). Increased to >=2 now.

I am not a fan of automated merges on things that go live - also no description is provided nor reasoning as to why is it important for this repository.

Well, first it might seem to be more convenient than it is important but we have good experiences in os-autoinst, openQA and others and the approach is helping to improve the quality and prevent unforeseen problems because unlike human reviewers mergify is very diligent to ensure that all necessary CI checks are not failed but also present as happened multiple times that CI checks were not triggered at all.