Adds command line modal to the code task in get started
What does this MR do and why?
- adds the last part of the feature: command line instructions
- add tracking
- see https://gitlab.com/gitlab-org/gitlab/-/issues/556427
Changelog: other EE: true
Screenshots or screen recordings
note The screenshots and text in the issue are out of date from the Figma SSOT: https://www.figma.com/design/BIBQ28gmn2wExOFg5HInWQ/Improvements-to-Get-Started--Learn-GitLab-?node-id=163-19210&p=f&t=8K6b13Q8QRz9eSfq-0
How to set up and validate locally
Note: This is covered by feature spec in this MR and jest as much as possible.
Click to expand
- Setup gdk to simulate SaaS - https://docs.gitlab.com/ee/development/ee_features.html#simulate-a-saas-instance and restart GDK
- Create a new group and project.
- In rails console, onboard that group that was just created
::Onboarding::Progress.onboard(Group.last) - In the gitlab admin UI, edit the group to be on an ultimate trial plan(edit button from
http://gdk.test:3000/admin/groups) - In rails console(
bundle exec rails c), change the trial, trial start and end date for the groupGroup.last.gitlab_subscription.update_columns(trial_starts_on: Date.today, trial_ends_on: 30.days.from_now, trial: true) - Go to the get started path for the group/project: For instance,
http://gdk.test:3000/logan225-group/logan225-project/-/get_started - To observe/test the copy functionality, you'll need to enable nginx/https on GDK - see https://gitlab-org.gitlab.io/gitlab-development-kit/howto/nginx/
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #556427
Edited by Doug Stull


