feat(semantic_release): ignore subgroup on release github remote #548
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Correct Github remote errors when releasing from GitLab to GitHub repository.
As we are switching from direct cloning of GitHub repository hierarchy to GitLab sub groups per startup, we can't use the
CI_PROJECT_PATH
anymore to guess the GitHub repo to push too has it contains the GitLab subgroup that doesn't exit on Github resulting on the "classic" error :Error: Command failed with exit code 128: git ls-remote --heads https://[secure]@github.com/SocialGouv/archifiltre/archifiltre-statistics.git remote: Not Found
The alternative could be using the
CI_PROJECT_ROOT_NAMESPACE
andCI_PROJECT_TITLE
to reconstituate the GitHub flat repository hierarchysee https://docs.gitlab.com/ee/ci/variables/predefined_variables.html