@jamill Would you have a moment to spare a second set of eyes here? I realize that you're not spending as much time with submodules these days, but you certainly still know more about them than I do. :)

Looks OK to me - and I think this matches the expected behavior. I might also suggest updating the comments for this function to clarify that this will fetch if there are missing commits. Thanks!

Thanks for the review! I restricted the fetch logic to the not found error, and changed the documenation comment to mention the new behavior. I also made a slight drive-by fix for a duplicate check in the clone side.

I'm noticing now that submodule update has a -no-fetch flag. Maybe there should be a no_fetch flag in the submodule update options? Probably not a big deal though.

I'm noticing now that submodule update has a -no-fetch flag. Maybe there should be a no_fetch flag in the submodule update options? Probably not a big deal though.

I agree, that would be a really nice option. Is this something you want to tackle in this PR or do you want me to merge this and tackle this later?

I guess that I should probably add it in this PR so that I don't forget it. I'll add it soon.

I added the flag. I also made another small drive-by fix to the version used in the update options initializer.

I also made another small drive-by fix to the version used in the update options initializer.

Good catch on that one. 👌 Thanks!