Skip to content

Allow execution of clientside hooks on actions taken with GitLab WebIDE

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Problem to solve

We have some groups, that would like to refuse commits, if commits are not according to some requirements ( for example a correct syntax of the files commited ) with the WebIDE. GitLab provides us serverside hooks, which can only be managed by an administrator and clientside hooks which will not work when commiting with the WebIDE.

Further details

The target usergroup is not experienced developers. Our goal is to make it as easy as possible for them, to take changes to certain projects. Having the ability to execute client-side hooks on commits done over the gitlab webinterface would be great. Editing and maintaining server-side hooks on the GitLab Server is a hazzle for the Administrators and allow the group members access to the server is not an option caused by security concerns.

Proposal

Please add the posibility to execute client-side hooks directly on the GitLab Server.

What does success look like, and how can we measure that?

Groups can edit their own client-side hooks in the project repository. The hooks are executed independently of the client ( WebIDE or dedicated gitclient )

Links / references

Edited by 🤖 GitLab Bot 🤖