You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.
Provides a pre-merge feedback flow which allows all stakeholders to be involved on reviewing the work that is getting done in a WI.
Description
OSIO provides simple interactions between all the stakeholders which might be involved on a particular WI. This epics will provide a seamless integration between a WI, Che workspaces and CI.
Sample Flow:
Dev starts working on a WI, clicks on "Start Coding" button
Che opens in a branch named for WI
Dev works the inner loop
Makes a commit against branch
Preview URL is published back to the WI
Reviewer gets notified of change in WI
Review is done and dev makes change, recommits
Dev does a push to their branch, triggers CI
CI completion adds CI job link, and notification in WI
Related: #718
We need to precisely author this entire experience (and it may require us to create more than one experience). During that time, let's discuss the merits of #718.
@slemeur okay if we close this in favor of #2715? We can continue to refine that Experience (or create sibling Experiences) which describe the user experience from WI to branch to Che and beyond.
Goal
Provides a pre-merge feedback flow which allows all stakeholders to be involved on reviewing the work that is getting done in a WI.
Description
OSIO provides simple interactions between all the stakeholders which might be involved on a particular WI. This epics will provide a seamless integration between a WI, Che workspaces and CI.
Sample Flow:
Implementing Features
Parent Scenario
#2062
The text was updated successfully, but these errors were encountered: