The way this will show up is when you do a git status from your main website repo, in the “Changes not staged for commit” section you will see your theme submodule listed and one of two statuses:
#Git submodule add update#
So you need to update where the main repo’s submodule commit HEAD points to. But in Step 3 you made changes and committed them. In the case of the initial adding of the submodule, it points to the head of the submodule. In your main hugo website repo, the submodule tracks the latest submodule commit you explicitly checked in. Step 4: update main repo with latest theme commit " to unstage ) new file: layouts/partials/categories.htmlįrom here you do your normal git workflow like status, add, commit and push. Your branch is up-to-date with 'origin/master'. Using your terminal app, cd into the themes directory of your website and run git submodule add with the URL of your forked repo, e.g.: We’re now ready to add the theme to our Hugo website. Step 2: add the forked repo to your website From that point forward, your interactions with the theme will be through your fork of the repo (e.g. Note, this assumes you have a github account and are logged in. Once you visit the theme’s webpage, follow the link to it’s github repo and fork the repo into your account. Step 1: Fork your targeted themeįor this blog, we’ll target the Mainroad theme.
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.
#Git submodule add install#
This works, makes sense and is the most common install instructions from the theme authors. This is meant to be a faithful conversion that leaves the behavior of ' cmd_add()' script unchanged.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. This new subcommand clones the repository that is to be added, and checks out to the appropriate branch.
#Git submodule add code#
Let's add a new " add-clone" subcommand to git submodule-helper with the goal of converting part of the shell code in git-submodule.sh related to git submodule add ( man) into C code. In practice, this does not change any behaviour, as no functionality in 'submodule add' and 'submodule update' relies on the value of the exit code.Īnd: submodule-helper: introduce add-clone subcommand Note that the shell version of die exits with error code 1, while the C version exits with error code 128.
Let's prefix each of the shell die messages with 'fatal: ' so that when they are converted to C code, the error messages stay the same as before the conversion. This does not happen with the die used in 'git-submodule.sh'. The standard die() function that is used in C code prefixes all the messages passed to it with 'fatal: '. (Merged by Junio C Hamano - gitster - in commit 10f57e0, ) submodule: prefix die messages with 'fatal' See commit 8c8195e, commit a98b02c, commit 0008d12 (), and commit 84069fc () by Atharva Raykar ( tfidfwastaken). See commit bbe3165 () by Jeff King ( peff). Note that this will slightly change With Git 2.33 (Q3 2021), with the rewrite of " git submodule" ( man) in C, which does impact git submodule add: gitmodules, preventing any " git submodule add" command to modify it. If it possible you had a process keeping an handle on your. I uninstalled and reinstalled it the error went away.Ĭonsidering the current version of git-submodule.sh fails on: if ! git submodule-helper config -check-writeable >/dev/null 2>&1 There was something wrong with my git installation. I assume it's just my poor understand of git. Looking for this error on Google just returns the source files with the error but no explanation to why I'm getting it. gitmodules file, but I get this error even if I create it by hand. Looking at the documentation, the first run of this command should create the. I want to add Foo as a submodule using git submodule add īut I keep getting "please make sure that the.
I've created a new empty project (root) and cloned it locally. I have imported a project (foo) into githib. We have a root project that just contains the references to all the external projects (submodules in git). I'm new to git, currently looking at porting some large projects from mercurial.
0 kommentar(er)
