Ensure git safe.directory command does not overwrite existing entries
What does this MR do?
Makes the safe.directory command additive.
-
Before this change:
Integration test fails:
2) running image with test project with js-npm with lockfile v1 issue-571828 behaves like successful scan exit code is expected to eq 0 Failure/Error: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts| raise failure } expected: 0 got: 1280 -
After this change:
Integration test succeeds
What are the relevant issue numbers?
Does this MR meet the acceptance criteria?
-
Changelog entry added -
Documentation created/updated for GitLab EE, if necessary -
Documentation created/updated for this project, if necessary -
Documentation reviewed by technical writer or follow-up review issue created -
Tests added for this feature/bug -
Job definition updated, if necessary -
Conforms to the code review guidelines -
Conforms to the Go guidelines -
Security reports checked/validated by reviewer
Closes #571828
Edited by Adam Cohen