I’m creating a custom sharedgitconfig file in one of the repositories of a project in bitbucket based on what I was able to read here. I’m a beginner, so please bear with me if these questions are fairly basic. The idea is that this repository will be cloned initially, and the developers will be able to use the infrastructure to make their changes to the code before using git aliases to automate some of the more tedious commands and naming schemes we have in place for things like Jenkins.

The issue I seem to be running into when I test with other developers is the constant need to include the custom config file in the path every time the repository is cloned. I understand that this is a requirement for the first time the repository is cloned as you have to set it up somehow, but is there a way to make this a one-time thing? Ideally this sort of configuration would only be used once when we first implement this into the project, and the developers will be able to use the aliases within without any hassle after.

Again, apologies if this is a bit of a redundant question. First time posting and haven’t found much insight in the posts from 10+ years ago. Not for lack of trying.