Skip to content

add `--checkout --force` options to `git submodule update --init`

What does this MR do?

This MR adds --checkout --force options to git submodule update --init

Why was this MR needed?

One of our developers added git submodule deinit . to after_script in .gitlab-ci.yml. After that subsequent jobs on this runner can't find any files inside submodule directory and failed. This errors was urgently fixed with addition git submodule update --init --force --checkout to before_script in .gitlab-ci.yml. Suddenly I can't reproduce the issue.

With --force flag working copy state will be more predictable.

Are there points in the code the reviewer needs to double check?


Does this MR meet the acceptance criteria?

  • Documentation created/updated
  • Tests
    • Added for this feature/bug
    • All builds are passing
  • Branch has no merge conflicts with master (if you do - rebase it please)

What are the relevant issue numbers?

Merge request reports