Waleed Khan

Thanks for reporting. This is similar to https://github.com/arxanas/git-branchless/issues/338 and https://github.com/arxanas/git-branchless/issues/694. I commented in #338: > The best solution is probably to not install the `branchless.core.mainBranch` setting to the same config...

Here's a test that reproduces the issue: ```patch From 238cdaa1e54552f3492096301e4edf96d87e7475 Mon Sep 17 00:00:00 2001 From: Waleed Khan Date: Mon, 24 Apr 2023 22:02:00 -0800 Subject: [PATCH] temp: reproduce issue...

Oof, it looks like it might be hard to fix this one. I don't really understand why `git undo` thought it was appropriate to delete the main branch in this...

Can you compare the resulting runtimes for running the whole test suite and running a single test? The improved compilation times are admirable, but if it turns out that the...

Regarding `touch`, @jyn514 would probably know better than me, but in my blog post I actually modified the file in the worry that `cargo` might do something content-addressed as part...

Do we have a concept of "pathsets" yet 🙂? Conceivably we would want to use all the same patterns in a revset to specify commits that do/don't touch a certain...

> In other words, would this be any different from running git status in a colocated repo? If `jj status` (and working tree snapshotting in general) itself calls `git status`,...

> would this be any different from running `git status` in a colocated repo? Well, I guess it depends on what you mean by "running `git status`". - `git status`...

Here's an example of what omitted commits look like in git-branchless: Note that the log is reversed and trunk commits are represented with an ellipsis *without* a commit count. (Also,...

@essiene I think we want `jj git init` to be equivalent to current `jj init --git-repo .`, and then hide/remove the current `jj init` (or make it only initialize with...