Support for orphaned branches
It looks like GKC does not support orphaned branches.
Repro:
1. Init a new repo, let GK make an initial commit
2. Drop to CLI, run 'git checkout --orphan dev'
3. See that GK isn't happy, doesn't want to load the repo anymore
because there's no initial commit on the current branch. This is a
separate bug, but still worth mentioning.
4. Run git commit -m 'Dev init'
5. Reload GK to see a commit graph with two separate branches sharing
no history.
6. Right-click on the other branch, see that the context menu doesn't
appear. Right-click on self, context-menu appears.
7. Switch branches, repeat 6. Same behaviour in the other direction.
Our repo has a "master" and a "dev" branch which were created from different states of the project when FTP was used for deployment (prod file state became master, demo/staging became dev).
Very frequently, I need to cherrypick commits from "dev" over to "master" when deploying, but if it's the latest commit, I can't, because no context menu appears.
Comments: 3
-
17 Dec, '21
Jonathan Admin"Support orphaned branches" (suggested by wczmatthew on 2021-12-16), including upvotes (1) and comments (0), was merged into this suggestion.
-
25 Aug, '22
John WeltyThere is no context menu on orphan commits. I see them and can get to them but can't copy branch name or anything like that.
Edit: Might just be my latest orphan commit. I have some others that are working. -
23 Sep, '23
HansThis featurer will be indeed very useful for example:
1) If you want to switch from private to a public project without history
2) For GitHub pages to initialize a `gh-pages` without previous history it will be super helpful.
Please, also consider a makro like:
```
git checkout --orphan new-branch
git rm -rf .
git commit --allow-empty -m "Initial commit"
git checkout back
```