Consider the placement of the download button in the Branch list
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=414462) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal Can we remove the "Download" button in the Branch list view? ![CleanShot_2023-06-06_at_23.10.08](/uploads/664467162ec2ba8cebcdef8125562a0b/CleanShot_2023-06-06_at_23.10.08.png) Need to understand why the list of artifacts need to be displayed in the Branch list view. Alternatively we could display the other download options in an overflow menu. The image below is a concept but we didn't implement this in !119637 because the list of artifacts could be really long. ![image](/uploads/f0cc06a76195a9bd68d9b33a15358ca9/image.png) <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->
issue