-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Eclipse Che team as reviewers to community devfile registry content #1498
Comments
Best to investigate which one of these works best first and choose the one that does. |
Trying to investigate the group solution and if we can have one approval per group. Will share an example from my fork soon. |
I've tried to look into a possible solution that requires approval from 2 CODEOWNERS coming from two different groups of users (
|
Given the decision from today's team meeting, we've decided to use the Will update the criteria in the description to match this. |
Created issue #1538 in order to add a new workflow job to check all updated stacks against dev workspaces |
Opened a PR to update the CODEOWNERS & OWNERS files. Also added a process for this section inside the contributing guide. |
Which area/kind this issue is related to?
/kind task
/area registry
Issue Description
Since Eclipse Che now uses the community devfile registry directly to acquire stacks for creating workspaces, we'll need to include the Eclipse Che team as reviewers to sign off on any stack changes by us, the community, or the Che team themselves which is now included under the Eclipse Che software by default.
Acceptance Criteria
CODEOWNERS
file for all stacks (as should be for Devfile Services Team if this is done)The text was updated successfully, but these errors were encountered: