Skip to content

Onboard devfile repositories to Mergify #1763

@michael-valdron

Description

@michael-valdron

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/alizerEnhancement or issue related to the alizer repoarea/apiEnhancement or issue related to the api/devfile specificationarea/ciarea/integration-testsEnhancement or issue related to the devfile integration testsarea/landing-pageIssues with the Landing Pagearea/libraryCommon devfile library for interacting with devfilesarea/registryDevfile registry for stacks and infrastructurearea/registry-viewerdevtools-weekkind/tasklifecycle/staleStale items. These items have not been updated for 90 days.

    Type

    No fields configured for Task.

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions