Enjoyneering

Enjoyneering

Share this post

Enjoyneering
Enjoyneering
Our usage of GitLab Code Owners

Our usage of GitLab Code Owners

Julien's avatar
Julien
Mar 01, 2023
∙ Paid
1

Share this post

Enjoyneering
Enjoyneering
Our usage of GitLab Code Owners
Share

As GitLab is our VCS, we used GitLab code owners. And you can discover more about it here on the GitLab website. But if you use another tool, you can have a similar feature (e.g., GitHub code owners, Bitbucket branch permissions…). GitLab code owners is a feature that allows teams to designate specific individuals or groups as the owners of particular files or directories within a Git repository.

As we have leveraged this feature for a few months, I can share our feelings about it, what it brings to the team, and what concerns we envision.

In this article, we cover the following:

  • Our usage of GitLab code owners

    • How we set it up

    • Our take on change’s criticality

  • Our view on the pros of using code owners

  • Our view on the cons of using code owners

  • Conclusion

Have a good read!

https://s3.us-west-2.amazonaws.com/secure.notion-static.com/4dfd0a58-d9bd-4cf2-94b1-c49c58e83e43/Untitled.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIAT73L2G45EIPT3X45%2F20230301%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20230301T173321Z&X-Amz-Expires=86400&X-Amz-Signature=6f258b62c847ebf1aa1667bb668e75fbe4d4d5faa369d82cb0a87de5b88c1807&X-Amz-SignedHeaders=host&response-content-disposition=filename%3D%22Untitled.png%22&x-id=GetObject
Batman: Let me review this Pull Request! Sheriff: No, you won’t! I own this scope!

This post is for paid subscribers

Already a paid subscriber? Sign in
© 2025 Julien
Privacy ∙ Terms ∙ Collection notice
Start writingGet the app
Substack is the home for great culture

Share