Replies: 1 comment
-
All is local (your project that is). Doks dependencies are listed locally (in package-lock.json) + are installed (and thus available) locally (including I would start fresh (that would really be the easiest way):
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I had used someone else's docs theme, hosted on netlify. Then decided to switch over to doks.
I want to push to the same repo I was using before. (At least I think that would be one way of not having to deal with DNS settings in netlify.)
I don't know how .git/config should look.
I don't quite understand upstream vs. I believe that some of the layouts only appear on your repository, and not locally. (at least I think that's the case.)
for now when I do:
% git push origin main
I get:
My .git/config currently looks like this mess, after too many experiments.
main
and notmaster
?[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
ignorecase = true
precomposeunicode = true
[remote "origin"]
url = [email protected]:mroswell/hugonewbie.com.git
fetch = +refs/heads/:refs/remotes/origin/
[branch "main"]
remote = origin
merge = refs/heads/main
#[branch "master"]
remote = origin
merge = refs/heads/master
#[remote "upstream"]
url = https://github.com/h-enk/doks-child-theme.git
fetch = +refs/heads/:refs/remotes/upstream/
#[branch "master"]
remote = upstream
merge = refs/heads/main
~
My troubles started when I went to push, and of course, I couldn't because it still had your repo as the remote. I quickly changed the remote, but somewhere along the way, I've lost my way...
Beta Was this translation helpful? Give feedback.
All reactions