Editing using GitLab interface
Background:
A new repo editor is being built to make it easier to contribute through the GitLab interface, particularly when editing multiple files.
What questions are you trying to answer?
What are the key frustrations of editing multiple files through GitLab?
Are you looking to verify an existing hypothesis or uncover new issues you should be exploring?
The existing hypothesis is that file tree navigation, a multi-file editor, and staging edits across multiple files in a single commit will significantly improve repo editing through the GitLab interface.
The community has clearly indicated that file tree navigation is important in issues and demonstrated by the Octotree browser extension.
Although editing multiple files through the GitLab interface is undoubtedly more laborious than using a local editor, the specific causes have not been researched. I would like to understand more specifically what issues users have with the current repo editor.
What is the backstory of this project and how does it impact the approach?
- https://gitlab.com/gitlab-org/gitlab-ce/issues/31890
- https://gitlab.com/gitlab-org/gitlab-ce/issues/13723
What do you already know about the areas you are exploring?
What does success look like at the end of the project?
Determine the key frustrations (and severity) GitLab users have when editing multiple files through the GitLab interface (not command line), to verify or adjust the scale and direction of the repo editor project.