Heath Stewart

Using reflog is a good idea. I wasn't successful with GQL without a lot of queries. I still think it better for GitHub to add an endpoint that could assist...

If we're settled on `gh-merge-base` (should probably "namespace" it like VSCode did; we could use `vscode-merge-base` later if we decide to support that scenario), anything holding up at least supporting...

Works for me. We might also want to consider adding that flag in a few other commands like `gh issue develop --base {string}` or anywhere you can specify a `--base`...

I've got a start on this but noticed something in the branch I created with just `git checkout -b issue8979` in the terminal, then opened VS (so the GitHub Pull...

Just saw this on your blog: could help locally with identifying the parent if you can dictate Horton versions: https://github.blog/open-source/git/highlights-from-git-2-47/#quickly-find-base-branches-with-for-each-ref

> I think that we'll still end up with this info duplicated by the built in git extension and by the gh CLI though. If we can agree on an...

Since vscode-merge-base is meant to be generic I can see not unifying but it might still be good for us to consider falling back to it if your algorithm is...

Thanks, @alexr00! But now I feel bad because it seems @williammartin already [found that](https://github.com/cli/cli/issues/8979#issuecomment-2321441899). 🤦‍♂️ Given that `github-pr-merge-base` is deprecated (IMO, I agree it might be good to remove to...

This extension doesn't use `cli/go-gh`, though maybe it should. This predated the project (or perhaps the necessary bits) and ref'd `cli/cli` itself, so maybe it's a good time to switch...

How did you download it? Did you run `gh extension install heaths/gh-label`? That's the only method supported for downloading `gh` extensions. Note, however, this really isn't needed anymore. There's a...