Skip to content

Support namespace scoping for git config file #710

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
isc-npetroce opened this issue Feb 20, 2025 · 2 comments · May be fixed by #762
Open

Support namespace scoping for git config file #710

isc-npetroce opened this issue Feb 20, 2025 · 2 comments · May be fixed by #762
Labels
customer Based on customer feedback (as opposed to something identified by developers)

Comments

@isc-npetroce
Copy link
Collaborator

We should permit having a different embedded-git-config.json on a per-namespace level in order to play nicer with production decomposition, as customers might configure separate local repositories for each namespace and pull into a single remote. Currently we only support having a global config file for the entire repo.

@isc-pbarton
Copy link
Collaborator

For more context, this is to support a monorepo where code for different namespaces is mapped to different subdirectories.
For example, classes for namespace1 are mapped to /namespace1/cls/ and classes for namespace2 are mapped to /namespace2/cls/.

The current workaround to support this is to add embedded-git-config.json to .gitignore

@isc-tleavitt
Copy link
Collaborator

This relates to #215 (really, this is what the customer wants, I think) and #312

@isc-tleavitt isc-tleavitt added the customer Based on customer feedback (as opposed to something identified by developers) label Feb 24, 2025
@isc-pbarton isc-pbarton linked a pull request Apr 29, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer Based on customer feedback (as opposed to something identified by developers)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants