CS Add-on: Update existing VSCode notice - Code Suggestions beta period is ending

Summary

Update existing VSCode notice to inform Code Suggestions users that beta period is ending

Problem

As we transition Code Suggestions to GA, current users should understand that the beta program is ending and what they need to do to continue to use the Code Suggestions feature. Many current Code Suggestions users are primarily working in VSCode and are less likely to see messaging in the GitLab product about the end of the beta period.

Solution

Update existing Code Suggestions VSCode notice copy to:

1. Message the end of the beta period for Code Suggestions
2. Include a CTA for users to learn more about how they can continue to use the feature

Prescendent & Resources

• The devopsmodelops team this original VSCode notice - We want to update the copy and add a CTA to this notice.
• VSCode Documentation for Notification UX

UX

Copy

• Notice copy:
• CTA:

User Experience criteria

• User can dismiss the notice

Questions

• It's been noted that VSCode can be fairly strict about what notices we place in their product - especially if we're selling something, which we in effect are trying to do here. Is this notice worth the potential risk of infringing/breaking their notification guidelines?
  • A: Per this discussion in the main epic, we'll refrain from any Sales-oriented messaging and simply communicate the end of the beta period with a CTA that directs to the website to learn more.
• Can the CTA we place in the VSCode notice direct into a specific group URL in Gitlab.com? We directed to a documentation link in gitlab-vscode-extension#817 (closed) - See video recording.
  • A: Yes, VSCode notices can direct to deep links. We will opt to keep the MVC solution simple and direct the user to a marketing site page with relevant information regarding the end of the beta period.