I don't know the answer, but here's something to check. Go to the .git
directory for your leo-editor repo, and look at the file named *config.* It
will tell you the branches that git knows about for your clone. Mine
starts like this:
[core]
repositoryformatversion = 0
filemode = false
bare = false
logallrefupdates = true
symlinks = false
ignorecase = true
[submodule]
active = .
[remote "origin"]
url = https://github.com/tbpassin/leo-editor.git
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master
[remote "upstream"]
url = https://github.com/leo-editor/leo-editor.git
fetch = +refs/heads/*:refs/remotes/upstream/*
[branch "6.2"]
remote = origin
merge = refs/heads/6.2
[branch "devel"]
remote = upstream
merge = refs/heads/devel
>From the git clone manual page:
"After the clone, a plain git fetch without arguments will update all the
remote-tracking branches, and a git pull without arguments will in addition
merge the remote master branch into the current master branch, if any"
Maybe you just need to do git fetch or git pull.
On Wednesday, October 19, 2022 at 1:17:18 PM UTC-4 [email protected]
wrote:
> I forked leo and then cloned my fork and then attempted to switch to the
> devel branch and it failed.
>
> Is there not a contributing section in the official docs that shows one
> how to get started?
>
> cmd.exe shell transcript follows:
> [snip]
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/7d74af64-b291-46f2-b777-c7c35f71b36an%40googlegroups.com.
