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

Fix Change of verbiage to helper text under the 'Import from Git' text box. #1311

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

tyraziel
Copy link

@tyraziel tyraziel commented Feb 4, 2025

What does this PR do?

This PR changes the verbiage of the helper text under the Import from Git text box.

What issues does this PR fix or reference?

If you have more than zero workspaces, the verbiage doesn't make sense.

Is it tested? How?

I ran the tests from the devfile command.

Release Notes

Verbiage update on Create Workspace page.

Docs PR

N/A

Copy link

openshift-ci bot commented Feb 4, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tyraziel

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@che-bot
Copy link
Contributor

che-bot commented Feb 4, 2025

Click here to review and test in web IDE: Contribute

Copy link

openshift-ci bot commented Feb 4, 2025

Hi @tyraziel. Thanks for your PR.

I'm waiting for a eclipse-che member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@@ -180,7 +180,7 @@ class ImportFromGit extends React.PureComponent<Props, State> {
validated={validated}
helperTextInvalid={errorMessage}
helperTextInvalidIcon={<ExclamationCircleIcon />}
helperText="Import from a Git repository to create your first workspace."
helperText="Import a devfile from a Git repository to create a new workspace or launch an existing one."
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tyraziel tbh, I think the wording might be a bit confusing

Copy link
Member

@ibuziuk ibuziuk Feb 5, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would probably opt-for smth. more simple:

  • remove mention of devfile
  • remove new / launch an existing one
  • replace workspace with CDE

@@ -180,7 +180,7 @@ class ImportFromGit extends React.PureComponent<Props, State> {
validated={validated}
helperTextInvalid={errorMessage}
helperTextInvalidIcon={<ExclamationCircleIcon />}
helperText="Import from a Git repository to create your first workspace."
helperText="Import a devfile from a Git repository to create a new workspace or launch an existing one."
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
helperText="Import a devfile from a Git repository to create a new workspace or launch an existing one."
helperText="Import from a Git repository to create a Cloud Development Environment"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like it.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think my main hangup is that if an environment of the same name already exists, it will ask if you want to open the existing one or create a new one. Trying to capture that concisely is the tricky part.

What if we changed it from "create" to "launch"? Does launch indicate create/open?

"Import from a Git repository to launch a Cloud Development Environment"

@ibuziuk @olexii4 ?

@ibuziuk
Copy link
Member

ibuziuk commented Feb 5, 2025

@tyraziel thank you for the first contribution \o/
please, sign Eclipse ECA - https://api.eclipse.org/git/eca/status/gh/eclipse-che/che-dashboard/1311

Copy link

codecov bot commented Feb 5, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.66%. Comparing base (1635623) to head (f316fc0).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1311      +/-   ##
==========================================
- Coverage   91.68%   91.66%   -0.03%     
==========================================
  Files         500      500              
  Lines       45482    45482              
  Branches     3164     3163       -1     
==========================================
- Hits        41700    41689      -11     
- Misses       3754     3764      +10     
- Partials       28       29       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@tyraziel
Copy link
Author

tyraziel commented Feb 7, 2025

@tyraziel thank you for the first contribution \o/ please, sign Eclipse ECA - https://api.eclipse.org/git/eca/status/gh/eclipse-che/che-dashboard/1311

I should be all set with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants