Conversation
olexii4
requested review from
a team,
deerskindoll,
gtrivedi88 and
mkuznyetsov
as code owners
September 9, 2026 14:06
|
🎊 Navigate the preview: https://6ab10651b83e9ea8ad9c7bc8--eclipse-che-docs-pr.netlify.app 🎊 |
|
Click here to review and test in web IDE: |
-525C86?logo=eclipse-che&labelColor=red){kind=icon}
Assisted-by: Claude Opus 4.6 Signed-off-by: Oleksii Orel <oorel@redhat.com>
3 tasks
gtrivedi88
added a commit
that referenced
this pull request
Sep 23, 2026
The dawidd6/action-download-artifact step in this workflow only specified 'workflow', not 'run_id'. Without run_id, the action searches for the most recent successful 'doc-content' artifact for that workflow name across the entire repository instead of the specific run that triggered this workflow_run event. allow_forks defaults to false, which additionally causes the search to skip fork-originated PR runs (every JTBD PR is opened from a fork). The net effect: preview links for fork PRs get attributed to whatever non-fork branch happens to have the most recent successful build, instead of the PR that actually triggered the workflow. Observed on PR #3143: multiple concurrently-building fork PRs (#3143, #3151, #3153, #3155) never received their own preview link; the '"Navigate the preview"' comment kept landing on PR #3192 (a same-repo branch push) instead, whose sticky comment was repeatedly overwritten with unrelated deploy links throughout the day (createdAt stayed 2026-09-09 while the body kept changing). Fix: pin run_id to github.event.workflow_run.id so the artifact download always resolves to the exact run that completed, and set allow_forks: true since this workflow already executes in the base repo's trusted context via workflow_run. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Adds a procedure page documenting how to change the IDE on a stopped workspace from the Overview tab, and adds it to the end-user-guide navigation under "IDEs in workspaces".
The page follows the same structure as the existing "Change the AI tool on a workspace" procedure: prerequisites, step-by-step instructions including the version picker, and links to related editor documentation. The procedure clarifies that editors are selected by identifier from the available editors list, not by custom container image.
Screenshot/screencast of this PR
N/A
What issues does this PR fix or reference?
fixes https://redhat.atlassian.net/browse/CRW-10647
Dashboard PR: eclipse-che/che-dashboard#1663
Is it tested? How?
ides-in-workspaces.adoc,defining-a-common-ide.adoc.Release Notes
Added documentation for changing the IDE on a stopped workspace from the dashboard Overview tab.
Docs PR
N/A (this is the docs PR)