It then gets tricky over time to merge changes from the master repo into your theme without losing any of your edits. Once you make the edit, you can’t issue a Pull Request because this is specific to you. However, you will likely run into an issue where you want to make an edit to the theme only for your website. This works, makes sense and is the most common install instructions from the theme authors. I just thought I would share the steps just in case.When I first started tinkering with Hugo for static website generation, I would find a Hugo theme that I like, cd into my themes directory and would simply git clone the repo into my website. Perhaps you have followed this process already and it works as expected for you? I'm not sure. This will update the submodule object in feature1 branch of the main repo, to point to the latest commit of release/v1.7 Commit your changes and push to the main repo. Then, run git submodule update -remote REPOĤ. gitmodules file in the branch to look as follows: ģ. Check out locally feature1 branch of the main repoĢ. branch release/v1.7, then you need to do the following:ġ. feature1 of the main repository to point to a specific branch of the submodule, e.g. The commit that is displayed there for each submodule is the one that will get cloned. feature1, navigate to the Source page of the repo on Bitbucket website, switch the branch from the dropdown to feature1 branch in order to see feature1's Source. If you have in the main repo a branch named e.g. Regarding the other question with the branches: You are very welcome, I'm glad to have helped! What is your requirement here? I'm not sure you mean by proper commit.ĭo you want your submodule to point to a branch other than its main one? If you have made any changes in the submodule, but you haven't updated the main repo to track the updated version of the submodule, then the submodule commit that will be cloned will not be the latest one (it will be the one displayed on the Source page of the main repo). This is the commit displayed on the Source page of the main repo, in the Bitbucket website. Will clone only the commit of the submodule where the main repo is pointing to (by main repo I mean the repo that uses the submodule). The other command you mentioned should also work: git submodule set-url - REPO following command: git submodule update -init -recursive -depth=1 test-repo instead of REPO in the above command. Then the command to update the URL in the yml file should be as follows: git config believe that the clone of the submodule may have been failing because you were using e.g. Many thanks again, this community is great, Or it is going to checkout just the default branch for each submodule. step : * Boudale could you confirm this solution? Because, I am not sure that it is going to checkout the proper commit of each submodule. '**' : #this runs as default for any branch not elsewhere defined git submodule update -init -recursive -depth=1 git config git submodule set-url - PROTO git submodule set-url - DEV_TOOLS/protobuf-c DEBIAN_FRONTEND="noninteractive" apt-get -y install git clang-format-12 In the git config command you are using in your yml file, does the my-submodule part include any capital letters?ĭepth : full # SonarCloud scanner needs the full history to assign issues properly.gitmodules file for the repo, do the submodule name and path have any capital letters or are they lowercase? Does the submodule repo perhaps have any capital letters in its name?.gitmodules (which doesn't include a username and app password) In this case, the url of the submodule is not changed, and the git submodule update command is using the url defined in. my-submodule.url not match the name defined in the. I have been able to reproduce this error though when the name used for the submodule in the following command (the my-submodule part) git config submodule. It doesn't look that the Docker image is the problem here, I have no issues updating the submodules when I use the Docker image you mentioned.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |