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.

Sign up for GitHub

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

Jump to bottom

When the git repository is on gitlab.com .che/che-editor.yaml is ignored #21562

Closed
Tracked by #20583
l0rd opened this issue Jul 19, 2022 · 0 comments · Fixed by eclipse-che/che-server#334
Closed
Tracked by #20583

When the git repository is on gitlab.com .che/che-editor.yaml is ignored #21562

l0rd opened this issue Jul 19, 2022 · 0 comments · Fixed by eclipse-che/che-server#334
Assignees
@vinokurig
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.

Comments

@l0rd
Copy link
Contributor

l0rd commented Jul 19, 2022

Describe the bug

If I configure Che OAuth with gitlab.com and then start a workspace from a gitlab.com Git repository (https://gitlab.com/mario.loriedo/microservices-demo-frontend for example) then the editor configured in file .che/che-editor.yaml is ignored.

Che version

next (development version)

Steps to reproduce

  1. Deploy Che and configure OAuth for gitlab.com
  2. Create a workspace from Git repository https://gitlab.com/mario.loriedo/microservices-demo-frontend
  3. Verify that the editor is Theia and not VS Code

Expected behavior

The editor should be the one specified in .che/che-editor.yaml

Runtime

OpenShift

Screenshots

No response

Installation method

chectl/next

Environment

Amazon

Eclipse Che Logs

No response

Additional context

No response
@l0rd l0rd added the kind/bug Outline of a bug - must adhere to the bug report template. label Jul 19, 2022
@l0rd l0rd mentioned this issue Jul 19, 2022
Closed
11 tasks
@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 Jul 19, 2022
@l0rd l0rd added area/git severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jul 19, 2022
@svor svor mentioned this issue Jul 19, 2022
Closed
51 tasks
@vinokurig vinokurig mentioned this issue Jul 25, 2022
Merged
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vinokurig vinokurig

Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Fix che-editor.yaml recognition eclipse-che/che-server
3 participants
@l0rd @vinokurig @che-bot