This message was deleted.
# bug-reports
s
This message was deleted.
a
cc @David Balatero who was playing with the shortcut Re: #2, we do have a beta for auto merge if you do want to opt in. cc @Jacob Gold
l
i'd love to opt in! i think i was in it previously but then i think the feature was rolled back?
d
@Lowell Bander it is unintentional, i will fix soon. I changed the shortcut to
L + G
but the key registration broke
we'll keep it as
L + G
fyi, sorry about the muscle memory adjust šŸ˜• but the rationale if you're curious is that
G
is a prefix that means
go
and in this case we're not going to github we're
Copying a [L]ink to [G]ithub
, and that was causing some confusion with others ("shouldn't
g
go to github?")
l
that makes sense!
v
Sorry for that, one voice was mine šŸ™‚ Also because it was not in the keyboard help with the other G+ ones
d
yeah, i'll make sure & add it to the keyboard help as well
sorry for the churn here!
v
the help already shows the new shortcut, just doesn't work šŸ™‚
d
hah great!
v
Well, the other way around would be more handy :-D
d
tbd on when it lands; i'm also working on fixes for • private github images 404ing on graphite • when someone pushes a new commit to graphite in the middle of you writing a comment it blows away your comment and you lose it (small % race condition, but bad nonetheless)
😮 2
but i'm hoping the kb shortcut registration is a quick fix