lobimontreal.blogg.se

git clone :main/main.git git submodule deinit child git rm child git add -all git commit -m 'remove child submodule'.

The parent project shows the submodule as having changes (still visualized as a change in commit hashes, because ignore = dirty). Start by cloning the parent repo and removing the old submodule. En este ejemplo, agregaremos una biblioteca llamada DbConnector. Para agregar un nuevo submódulo, use el comando git submodule add con la URL del proyecto que desea empezar a rastrear. Submodule has different commit checked out than recorded in parent project, working directory is dirty. Comencemos agregando un repositorio de Git existente como un submódulo del repositorio en el que estamos trabajando.The parent project shows the submodule as having changes (visualized as a change in commit hashes). Submodule has different commit checked out than recorded in parent project, working directory is clean.The parent project shows the submodule as having no changes (since ignore = dirty). The nice front-end interface, git show, cannot show subproject commit hashes This seems like a bug.) This happens regardless of whether there is a branch setting.

or git rev-parse :0: to see it.

The parent project shows the submodule as having no changes.

Submodule has same commit checked out as recorded in parent project, working directory is clean (no modified or untracked files).

These are the possible states for the submodule, and the status in the parent project with the setting ignore = dirty: In this example, we’ll add a library called DbConnector. To add a new submodule you use the git submodule add command with the absolute or relative URL of the project you would like to start tracking. where the parent project points to commit C but the submodule currently has commit F checked out. Let’s start by adding an existing Git repository as a submodule of the repository that we’re working on. What will not be ignored is a difference in the checked-out commit, e.g. if it has tracked files with modifications that have not been committed, and/or new untracked files), such changes will be ignored. In the context of the ignore = dirty setting for submodules, this means that if the submodule is dirty (i.e. Visual Studio Team Services (TFS Online) and On Prem-TFS (since TFS2015) both now have a good understanding of how submodules work and can now do CI Builds that incorporate submodules right out of the box. The term "dirty" here means the same as it does elsewhere in Git: the repo in question has tracked files (files that have previously been committed) that have modifications that have not been committed, and/or there are new untracked files. Much has changed at Microsoft in relation to Git in the last few years.