<!--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=362067) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal Please provide some means in the Web-IDE to set the execute flag for files. This is needed for the following examples: 1. In https://gitlab.com/juergen.kosel.jk/gcc-coverage-example/-/merge_requests/5/diffs the script `hello_world.sh` has been added by the Web-IDE. But the pipeline fails because this script has no execute flag. 2. Some of my colleges work on Windows. So they have no means to set the Linux file permissions. The current workaround for this would be, to clone the repository to some Linux PC and then run: ```bash chmod +x hello_world.sh git add hello_world.sh git commit -m"Set exec permission" ``` <!-- 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: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->