How to handle multiple user configs in git?

@darion 

There are a few ways to handle multiple user configs in Git:

1. Using global and local configurations: Git allows you to set both global and local configurations for user information. Global configurations are set using the git config --global command and apply to all repositories on your system. Local configurations are set using the git config command without the --global flag and apply only to the current repository. By setting different configurations at the global and local levels, you can easily switch between multiple user profiles.
2. Using conditional includes in the .gitconfig file: You can create a separate .gitconfig file for each user and then include these files conditionally in your main .gitconfig file based on certain conditions. For example, you can include a specific user's configuration file based on the path of the repository. This allows you to easily switch between configurations based on the repository you are working in.
3. Using aliases: You can create aliases in your .gitconfig file that set user-specific configurations when invoked. For example, you can create an alias called gitconfig-user1 that sets user-specific configurations for user 1, and then use this alias whenever you want to switch to user 1's configuration.
4. Using environment variables: You can use environment variables to set user-specific configurations in Git. For example, you can set the GIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL, GIT_COMMITTER_NAME, and GIT_COMMITTER_EMAIL environment variables to the user-specific values you want to use, and Git will use these values when making commits.

Overall, the best approach to handling multiple user configs in Git will depend on your specific workflow and needs. Experiment with these methods to find the one that works best for you.