-
Notifications
You must be signed in to change notification settings - Fork 162
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Makefile: git submodule detect and warn if out-of-sync #20
Conversation
It is a reoccuring issue that git submodule gets out-of-sync, which cause confusion and issues. End-user needs to run: git submodule update We cannot run this automatically, because there are legimite reasons for the submodule to be out-of-sync, e.g. when testing local changes. Thus, this patch detect SHA-1 doesn't match, and just warns end-users, together with a hint to call: git submodule update Signed-off-by: Jesper Dangaard Brouer <[email protected]>
It is a reoccuring issue that git submodule gets out-of-sync, which cause confusion and issues. End-user needs to run: git submodule update We cannot run this automatically, because there are legimite reasons for the submodule to be out-of-sync, e.g. when testing local changes. Thus, this patch detect SHA-1 doesn't match, and just warns end-users, together with a hint to call: git submodule update Signed-off-by: Jesper Dangaard Brouer <[email protected]>
Per discussion in PR #18 |
Erm, GitHub seems to think the commit is empty? |
LOL - It seems I forgot got call |
I fixed it in the stg branch, and ran |
Jesper Dangaard Brouer <[email protected]> writes:
I fixed it in the stg branch, and ran `stg publish` again. This
resulted in two commit's one empty and the new with same text and
contents. I'll try push a new branch, with a clean history.
No worries, I can squash those when merging; going to do a bit of
cleanup of the Makefile anyway :)
|
I will close this one, in favor of PR #21 |
- Previous update broke CI git checkout - CI was not testing pushed code - Update makefile to build C code before uTests to fix error: "/usr/bin/ld: cannot find -lwrapper"
It is a reoccuring issue that git submodule gets out-of-sync, which cause confusion and issues.
End-user needs to run: git submodule update
We cannot run this automatically, because there are legimite reasons for the submodule to be out-of-sync, e.g. when testing local changes.
Thus, this patch detect SHA-1 doesn't match, and just warns end-users, together with a hint to call: git submodule update