Closed cjnovak98 closed 1 month ago
@mriensch removed redundant bare repos in #22 but this still doesn't fix the root of this issue, which is needing to ensure that any vars either copied over or somehow eventually make it into the git file structure are all bare repos so we never have any issues with users trying to push to the git registry in the future.
New update: After discussing with the team, and determining a path forward, it is clear we need to follow a similar structure to how we are handling mirrored content - within the current /content directory, we will create a "git_repo" folder, which is where mirrored git repos will go, and later be uploaded on the disconnected side.
The logic for this should be smart enough to not add any additional variables and potentially piggyback off of the current mirroring stuff.
Title is fairly descriptive.
If we wrote something to always ensure that the git repo role can be ran multiple times without breaking anything, we can also make it so it automatically fixes any "broken" repos that have been copied over without removing the working tree via making the repo a bare repo.