Skip to content
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

Usability: Allow to Edit Workspace Commands #15239

Closed
tsmaeder opened this issue Nov 20, 2019 · 6 comments
Closed

Usability: Allow to Edit Workspace Commands #15239

tsmaeder opened this issue Nov 20, 2019 · 6 comments
Labels
area/plugins kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/duplicate Issue identified as a duplicate of another issue

Comments

@tsmaeder
Copy link
Contributor

In the context of adjusting the self-hosting devfiles to my concrete needs, I'd like to adjust the devfile commands, for example to use different directories.
Currently, I have to stop the workspace, change the command and restart the workspace for each change (which can be tedious especially if my changes don't immediately work)

I would propose a way to edit the commands from within the IDE. We could restrict editing in a way that makes it less likely that we break something in the devfile.

@tsmaeder tsmaeder added the kind/enhancement A feature request - must adhere to the feature request template. label Nov 20, 2019
@tsmaeder
Copy link
Contributor Author

Related: #13989

@tsmaeder tsmaeder added the area/editor/theia Issues related to the che-theia IDE of Che label Nov 20, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Nov 20, 2019
@benoitf
Copy link
Contributor

benoitf commented Nov 20, 2019

@tsmaeder devfile commands are transformed into tasks and you can edit tasks ?

@tsmaeder
Copy link
Contributor Author

@benoitf

  1. will that be persisted in the devfile?
  2. That link is not obvious.

@benoitf
Copy link
Contributor

benoitf commented Nov 20, 2019

@tsmaeder
for 1. no

I think this issue is already handled by wider epic issue: #12709

@benoitf benoitf added status/duplicate Issue identified as a duplicate of another issue and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Nov 20, 2019
@azatsarynnyy azatsarynnyy added area/plugins and removed area/editor/theia Issues related to the che-theia IDE of Che labels Feb 6, 2020
@azatsarynnyy
Copy link
Member

relabeled to area/plugins as it's related to https://github.com/eclipse/che-theia/tree/master/plugins/task-plugin

@che-bot
Copy link
Contributor

che-bot commented Aug 21, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 21, 2020
@che-bot che-bot closed this as completed Sep 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/plugins kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/duplicate Issue identified as a duplicate of another issue
Projects
None yet
Development

No branches or pull requests

4 participants