-
Notifications
You must be signed in to change notification settings - Fork 75
Add support for automated comments in stack update PRs #1757
Copy link
Copy link
Closed as not planned
Labels
area/ciarea/registryDevfile registry for stacks and infrastructureDevfile registry for stacks and infrastructurekind/tasklifecycle/rottenRotten items. These items have been stale for 60 days and are now closed.Rotten items. These items have been stale for 60 days and are now closed.lifecycle/staleStale items. These items have not been updated for 90 days.Stale items. These items have not been updated for 90 days.
Metadata
Metadata
Assignees
Labels
area/ciarea/registryDevfile registry for stacks and infrastructureDevfile registry for stacks and infrastructurekind/tasklifecycle/rottenRotten items. These items have been stale for 60 days and are now closed.Rotten items. These items have been stale for 60 days and are now closed.lifecycle/staleStale items. These items have not been updated for 90 days.Stale items. These items have not been updated for 90 days.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
Done ✅
Which area is this issue related to?
/area ci
/area registry
Issue Description
According to our LIFECYCLE.md & CONTRIBUTING.md files each Stack Update PR needs to be reviewed by the Stack Owner and the Eclipse Che team.
This needs to be clear in every PR. That said we could create an automation that notifies the PR author about our process. We could also revisit the Openshift CI automated comments and see if there's anything we could update there.
Acceptance Criteria
Target Odo Version
Target Odo version: