This message was deleted.
# how-do-i
s
This message was deleted.
j
unfortunately, we aren't compatible with
git-branchless
in this way
n
in which way is it incompatible?
j
does
git-branchless
create branches for each commit?
n
no, it doesn't create branches
j
Yeah, that would be the blocker here then
n
but you can manually create branches (and you have to, if you want to make pull requests)
j
ah i see — after doing that then yes, you could
track
and then
submit
n
ok, cool
one of the nice things about git-branchless, other than the workflow it supports, is that it has a custom implementation of
rebase
that's lightning fast
so a restack of a complicated commit tree takes just a second or two
j
yeah, i actually started reading through those docs just now bc i saw them when i was referencing to answer your question
we're looking at improvements to our own rebase flow and i'm trying to figure out if we can reuse any of that
n
Yeah, there's a couple things I really like about
git-branchless
that it seems might not be present in `gt`: • it's under
git
, rather than its own CLI tool (seems like
gt
could almost do this, except • super fast rebase •
git undo
is magical • available from
apt
/ doesn't require
node
👍 1
I guess I have this (irrational?) fear that I will forever be typing
gt
when I mean
git
and vice versa. Is it possible to rename
gt
to
git
so everything "just works"? How does the pass-through of unrecognized commands (e.g.
gt clone
->
git clone
) work? Glancing through
gt --help
it seems like the only subcommand collisions are
branch
,
commit
, and
log
j
it is possible to use
gt
for everything as we do pass through (although you enter node-land for this, so it isn't blazingly fast... yet), but idk if i've heard from anyone that aliased
gt
to
git
n
Seems to work:
Copy code
% git clone
Passing command through to git...
Running: "git clone"
Hm, but some commands don't get passed through:
Copy code
% gt config
Graphite is a command line tool that makes working with stacked changes fast &
intuitive.

[... help text ...]

Unknown argument: config
I guess I assumed it would pass through any unknown arguments - is there a way to get it to do that?
j
there isn't, i'm afraid
n
ah, so it's just a certain set of commands?
👍 1
j
Yeah, definitely something we can improve though!
n
Here's another one that I thought would work:
Copy code
$ gt checkout main
...

Unknown arguments: checkout, main
Also I do just want to say that I think the Graphite system is super cool! I am setting it up so our team can try it out. I'm posting here about some things I'm learning about it but I don't want it to seem like it's all complaints 🙂