Saul Salazar

Repositories git-access-control (users and teams) git-repositories (repos and groups) Why separate repos Separation of concerns principle. Least Privilege principle. Terraform works faster. A few rules/scenarios: An user can be a member of more than one team GitLab Permissions and Roles Reference: https://docs.gitlab.com/ee/user/permissions.html#project-members-permissions I recommend giving the developer access because otherwise the next role would be maintainer and they can delete things, manage users, edit project settings, edit branch protection and manage gitlab pages (domains and certificates) GitLab Modules Example # repo: git-access-control module "team_example" { source = ".

I realized moments before publishing that this article sounds like Documentation / Docs as Code but you can call it whatever you want :D Problems How to write technical documents? (at large scale company) How to find information faster? (to increase productivity) How to separate different information? (security purposes) Solution Use the same workflow developers already know and love (Git) and write documentation using plain text (Markdown), let the docs be easily written on the favorite editor of anyone.

Make employee onboarding easier providing a tool with a single command to install all required applications and plugins. The tool is Make so you just need to write a single file (the Makefile). Depending the case, this can be implemented for the entire tech area, the development division, multiple teams, or even big projects. Plus you can add ASCII art What you can automate Create default folders (notes, projects, documentation, temp).