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
Currently, gitpod.yml defines some "tasks", which are arbitrary processes which are fetched and integrated into the IDE or editor. However, JetBrains users are often heavily reliant upon run/debug configurations, using these configs as the preferred means for starting an application "task". There are also implications of using run/debug configurations (outside of the benefits of the feature, more generally) such as the enhanced UI behaviors on the run/debug views within JetBrains IDEs (such as better viewing of ports, and port forwarding functionality). There is therefore some design "conflict" between the Gitpod philosophy of tasks, and the way JetBrains users expect to use JetBrains. The purpose of this issue is to investigate how we can better integrate run and debug configurations into Gitpod.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Currently, gitpod.yml defines some "tasks", which are arbitrary processes which are fetched and integrated into the IDE or editor. However, JetBrains users are often heavily reliant upon run/debug configurations, using these configs as the preferred means for starting an application "task". There are also implications of using run/debug configurations (outside of the benefits of the feature, more generally) such as the enhanced UI behaviors on the run/debug views within JetBrains IDEs (such as better viewing of ports, and port forwarding functionality). There is therefore some design "conflict" between the Gitpod philosophy of tasks, and the way JetBrains users expect to use JetBrains. The purpose of this issue is to investigate how we can better integrate run and debug configurations into Gitpod.
Related:
The text was updated successfully, but these errors were encountered: