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

Document the Che-specific features we've added to Che's IDEA editor #21841

Closed
azatsarynnyy opened this issue Nov 25, 2022 · 1 comment
Closed
Labels
area/doc Issues related to documentation kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.

Comments

@azatsarynnyy
Copy link
Member

azatsarynnyy commented Nov 25, 2022

Is your task related to a problem? Please describe

In the Che-IDEA project, we extended the vanilla IntelliJ IDEA with the Che-specific features and made some adaptations of IDEA's internals to the Che environment.

While it does everything the user might expect from IDEA running in Che, there's no way to read the details of using the particular feature and learn about some important aspects of its behavior.

Describe the solution you'd like

We need to document all the Che-specific features, we've added to our IntelliJ IDEA assembly, on the Che documentation website.

Describe alternatives you've considered

No response

Additional context

Below is the list of the features we can consider to document:

  • running the Devfile Commands as IDEA's Launch Configurations with the possibility to run them in any container
  • opening IDEA terminals to DevWorkspace containers
  • detection of the opened ports and suggestions exposing corresponding apps' URLs
  • navigating to Che Dashboard from the IDE
@azatsarynnyy azatsarynnyy added kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. team/editors area/doc Issues related to documentation labels Nov 25, 2022
@che-bot
Copy link
Contributor

che-bot commented Jun 7, 2023

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 Jun 7, 2023
@che-bot che-bot closed this as completed Jun 14, 2023
@azatsarynnyy azatsarynnyy reopened this May 3, 2024
@che-bot che-bot closed this as completed May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/doc Issues related to documentation kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

3 participants