Browse feature should support previewing additional file types
Insight
The Browse feature needs to support previewing more file types when there is not a GitLab pages environment associated with that project, so that developers don't have to download massive artifacts. Customers were confused why they couldn't open a text file within the browser, for example, as all of our repo files can be seen within the browser. It is painful to have to download all build artifacts to be able to open them and view them.
A good example:
Project with GitLab pages environment - JSON file opens up in a GitLab Pages environment and renders the JSON as actual JSON.
Project without GitLab pages environment - TXT file - if GitLab Pages isn't set up on a project, instead of rendering the file as plain text we just download the file. Customers want to see the contents of the file in the browser without having to download it because those files could be very large.
Supporting evidence
Even just, even if it's a, are we can see it's a UTF eight files or display it as plain text would be, would be nice.
artifacts will be included browser. So I don't have to download this jar. And later on zip jar and compare, which class was changed or something like this
would really prefer it to be able to view it on the page. It works for the PDF and probably that's the only extension which is rendered on the page.
It depends on what job it is. If it is like, you know, creation of jar, probably there is no, no much needs except comparing, but you know, if we're talking for example about test job and I would like to create reports, maybe coverage reports, anything like that, you know, I would like to see an option to just view it. So probably like I frame where, you know, you could see how the page would look like.
I also used the artifact expos as attributes in order to be able to see the FYS quicker. So without having to go to the jobs and so on, but it's still not that great in terms of UI, because when you use the expos as for artifacts and you click on the file, it is just downloaded. So if we use techs to files, which is not as user-friendly, for example, as an embedded file, one of the options would be to be able to just collapse or open the file from this UI model to be able to read the peelings output, for example. So that could be another. So the fact that you need to download and save the file, then open it when you expose an artifact, is, is a bit cumbersome. So far, some real simple file types. It would be easier to be able to see them just as a file, for example,
Action
Support previews for additional file types in the browse feature, even when GitLab pages isn't set up for that project. A good example would be .txt
files.
Resources
Tasks
-
Assign this issue to the appropriate Product Manager, Product Designer, or UX Researcher. -
Add the appropriate Group
(such as~"group::source code"
) label to the issue. This helps identify and track actionable insights at the group level. -
Link this issue back to the original research issue in the GitLab UX Research project and the Dovetail project. -
Adjust confidentiality of this issue if applicable