Add `New from...` option when creating a Snippet
Problem to Solve
Many users have existing Snippets on other services because GitLab Snippets lacked parity with those other services. As GitLab has expanded it's feature set more for Snippets there is more parity.
Now that there is parity users can't easily move their Snippets from other services to GitLab without creating a Snippet on GitLab, checking it out locally, pushing their other Snippet and rewriting history.
Proposal
We should make it easy for users to create a Snippet from an existing git endpoint. By using the split-dropdown we can continue to have the primary action be create a new Snippet, and then a secondary option can be New From...
which would allow a user to provide a git endpoint that we would import as the Snippet.
UX Proposal
Description | Mockup |
---|---|
Replace New snippet buttons with split button (sniipets list and snippet details pages) |
|
Import snippet form | |
Import snippet in progress | |
Import error |
What's not in scope
Building a comprehensive importer for wholesale migration efforts as outlined in #22674 (closed). While an importer may make sense, this provides a lower friction way to be more selective about this at potentially a much lower effort.