Skip to content

Configure script overwrites existing embeded-git-config.json file #819

@cambot

Description

@cambot

I have noticed that when I run the Configure() script and choose the option to clone a repository, the embeded-git-config.json present in the clone gets overwritten by the Configure() script. This means we need to take the extra step of discarding the change and running "Import All (force)" to ensure that our source code is loaded correctly into a target environment.

We have Mac and Linux environments that are pretty locked down, so this step turns into additional steps because the git checkout is owned by irisusr and our developers cannot simply run git reset --hard HEAD.

  1. At a minimum, if "Clone Repository" is selected, I do not believe it should export a config file based on what was selected in the setup prompts.
  2. If you ask this question earlier (and the answer is yes), I think you can simplify the configuration flow by skipping questions whose answers end up in the config file.

Module Version: 2.12.2

Metadata

Metadata

Assignees

Labels

customerBased on customer feedback (as opposed to something identified by developers)

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions