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
Content from Eclipse Che might be irrelevant for devfiles
The following docs were adapted from Eclipse Che, and therefore, some large chunks of content might not pertain to devfiles or might need serious revisions in order to make sense in context of devfiles:
Determine the role endpoints and ports have in devfiles. This doc was very focused on Che UI and devfiles have no UI. Lines 5, 62, and 74 were Che UI focused. Verify that the edited versions still make sense and add meaning to the content.
Line 11. The original talked about Che workspaces. Devfiles don't have workspaces so confirm if the current content is till relevant.
Lines 24 and 36, prod-short initially referred to Che. So we can't simply replace it with "devfiles." Check these sections and the entire doc to make sure the use of "devfiles" still make sense.
Lines 81: verify if we can use "devfiles" here. We probably can't substitute "Che" with "devfiles" and have it make sense. Also, verify that the example is still relevant. Does devfiles even have a "sleep command" and "infinity argument"?
Line 37. For the subheading, we say "Parent referred by a URI" But the example uses a URL. If we use URIs, we might need a different example.
Additional context
See the conversations and commit history in the following doc PRS for more details on specific areas of content that were taken from Eclipse Che.
Content from Eclipse Che might be irrelevant for devfiles
The following docs were adapted from Eclipse Che, and therefore, some large chunks of content might not pertain to devfiles or might need serious revisions in order to make sense in context of devfiles:
Additional context
See the conversations and commit history in the following doc PRS for more details on specific areas of content that were taken from Eclipse Che.
The text was updated successfully, but these errors were encountered: