Onboard devfile repositories to Mergify #1763
Description
Which area is this issue related to?
/area ci
/area api
/area library
/area registry
/area registry-viewer
/area alizer
/area integration-tests
/area landing-page
Issue Description
As part of the effort to onboard our repositories to use Mergify's merge queue service (#1762), we'll need to onboard our devfile component and service repositories follow the guide: https://docs.mergify.com/merge-queue/setup/
Acceptance Criteria
- Onboard devfile/api to Mergify
- Onboard devfile/library to Mergify
- Onboard devfile/registry to Mergify
- Onboard devfile/registry-support to Mergify
- Onboard devfile/devfile-web to Mergify
- Onboard devfile/registry-operator to Mergify
- Onboard devfile/alizer to Mergify
- Onboard devfile/integration-tests to Mergify