2

I think I messed up...
I am reorganizing all of our code into aproppiately mantained repos, and I've been using submodules.
While I was creating repos, I noticed the option to use SHA256. I thought it could be interesting to try in some low-stakes, uninteresting repos (specifically, 2).
So now I gotta add one of those as a submodule to another repo. Of course, parent repo uses SHA1. And now I find out I can't...
It adds them, but thinks they've been modified. Expected hash mismatches checkout hash, because one of those got truncated... so I am left with those "modified" marks on "git status" permanently...
So, I screwed up? I thought this was possible. Bummer.

Comments
  • 1
    My advice: Don’t add projects that you actively work on as submodules.
    If it‘s a shared dependency, use a package manager instead.
  • 2
    @Lensflare Why not? I am pretty sure they are a solution to our use case, but I'm interested in why the recommendation?
  • 2
    @Lensflare I also would like to know why submodules are a bad idea for development, I'm considering using them
  • 3
    And also don't break out submodules at all until you really need to. Microservices are a maintenance nightmare, as are shared internal corporate libraries.
  • 1
    @c3r38r170 @lorentz
    When you are frequently making changes to the code that is in a submodule, you need to update the reference to the submodule on the repo that contains it.
    I find that very cumbersome and annoying.
    Using a package manager is less annoying because you can configure it to auto update the dependency.

    Though it may depend on what package manager you use and maybe also what git client you use.
  • 1
    Sorry for fucking up dolphin in the middle of your debug process :P
  • 0
    @retoor hahaha no need to apologize. Seriously.
Add Comment