<!--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=34977) </details> <!--IssueSummary end--> ### Problem to solve Installing custom pre-receive hooks is currently not possible on Gitlab.com, [see this support ticket](https://support.gitlab.com/hc/en-us/requests/135301). ### Intended users * [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead) * [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer) * [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer) ### Further details We at Midori develop productivity apps for Atlassian products (Jira, Confluence, Bitbucket). One of our apps is [Better Commit Policy for Jira](https://www.midori-global.com/products/better-commit-policy-for-jira/server/) that verifies the changes committed to Git, Bitbucket, GitHub, GitLab, Subversion & Mercurial against configurable rules. A code change management tool like this is typically used by corporations in highly regulated industries like healthcare, finance or aviation. Our tool is critical for product teams that are under frequent scrutiny by regulators, and need to strictly control that only compliant changes are committed to their repositories and the changes are clearly traceable, follow a preset format and only touches part of the code that is supposed to. See [this success story](https://www.midori-global.com/blog/2018/08/08/5-commit-rules-you-can-learn-from-developers-at-Philips) featuring Philips or [this](https://www.midori-global.com/blog/2018/05/28/eaglepicher-technologies-fulfills-faa-software-requirements-with-commit-policy-plugin), featuring EaglePicher, a battery manufacturer for the aviation industry. We frequently get questions from our users about how to use our app with GitLab.com, because many of our users are both Jira and Gitlab users. We have been working to make our apps compatible, so we can serve our mutual customers better. We hope that you will work with us, so software teams will be able to leverage Gitlab's features together with their Jira environment. ### Proposal In order for our app to work with Gitlab.com repositories, our hook scripts would need to be installed in the Git repository managed by GitLab.com. ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?--> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements If this feature requires changing permissions, this document https://docs.gitlab.com/ee/user/permissions.html must be updated accordingly. --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further help: https://about.gitlab.com/handbook/engineering/quality/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? <!-- Which leads to: in which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Links / references