In regards to the ambiguity of "git status" saying "new commits" when in fact you went back in time: If you do "git status --submodule" it will show you which commits are removed/added in the submodule (along with the regular output of "git diff").
@anthonywritescode3 жыл бұрын
nice tip!
@almasabdrazak50893 жыл бұрын
always like your explanations. One more use case. We are using protobuffs as a serialization protocol and for it to work you have to have a proto buff files in a repo, so we made one repo and share it between frontend and backend so our proto buffs are always in sync between services
@anthonywritescode3 жыл бұрын
makes sense! this fits into the "There isn't a package manager for this" use-case -- at a previous company we jammed protos into a pypi package to distribute it!
@samibadawi13156 ай бұрын
A long overdue thanks!!!
@a_maxed_out_handle_of_30_chars3 ай бұрын
your videos are too good, can you please create git specific playlist?
@rickylim49103 жыл бұрын
I totally agree with the pain of git submodules. Regardless of its pain, thank you for the explanation :)
@oliversheridan-methven8906Ай бұрын
Something comparing submodules with subtrees would be nice.
@kenpinzky47983 жыл бұрын
Git ! For the totally insane
@anthonywritescode3 жыл бұрын
true true, submodules are wack
@chandanagrawal2399 Жыл бұрын
If you make a change in one of the files of 'astpretty' while being inside 'empty' repo, would be be able to push that change to 'remote astpretty'?
@anthonywritescode Жыл бұрын
you generally shouldn't, but yeah you can make changes inside a submodule