https://linen.dev logo
Join Slack
Powered by
# feature-requests
  • s
    This message was deleted.
    👀 1
    d
    j
    • 3
    • 4
  • j
    something like 
    gt undo restack
    . I want to undo last restack and change my local state to its previos version stack. useful for the infrequent – but not rare – base rebase
  • s
    This message was deleted.
    p
    • 2
    • 2
  • s
    This message was deleted.
    p
    • 2
    • 1
  • s
    This message was deleted.
    👀 1
    p
    • 2
    • 2
  • s
    This message was deleted.
    p
    • 2
    • 1
  • s
    This message was deleted.
    ➕ 1
    d
    j
    • 3
    • 3
  • s
    This message was deleted.
    ➕ 3
    t
    j
    p
    • 4
    • 3
  • e
    I know that 
    gt checkout
    doesn't pass through to 
    git checkout
    . I would love though if it could be used with the 
    --ours
    / 
    --theirs
    option for resolving rebases, since restacking often ends up in resolving merge conflicts this way
  • s
    This message was deleted.
    ➕ 4
    j
    j
    • 3
    • 2
  • m
    When using 
    Merge when ready
    with the merge queue it waits with rebasing a pull request until the build has succeeded. This seems like a reasonable conservative choice but it would be nice to be able to tell it to rebase as soon as it sees that the PR is out of date with main so that if all the tests are going to pass it will be ready to merge sooner rather than later (i.e., having to wait for only one set of tests to run instead of two)
  • s
    This message was deleted.
    p
    • 2
    • 1
  • s
    This message was deleted.
    j
    • 2
    • 1
  • s
    This message was deleted.
    p
    • 2
    • 1
  • s
    This message was deleted.
    🥞 1
    k
    t
    f
    • 4
    • 5
  • s
    This message was deleted.
    j
    x
    • 3
    • 2
  • f
    I think 
    gt mergetool
    should redirect the command to 
    git mergetool
  • s
    This message was deleted.
    p
    x
    • 3
    • 3
  • s
    This message was deleted.
    t
    j
    • 3
    • 2
  • s
    This message was deleted.
    ➕ 1
    t
    • 2
    • 1
  • v
    Hello there! I don't know if this has been suggested before but I would love to have an easier way to select changes that should go into a commit. I see that currently you offer either selecting the whole uncommitted set of changes or selecting specific hunks. When I have a large number of changes and I only want to select a couple of hunks that I need to add to the current commit, I end up having to go through a long list of changes that I do not want to commit by pressing 
    n
    . Instead I suggest an approach that is popularized by tools like lazygit where a list of all the changed files are shown and you allow selecting the files (and offer selecting hunks within that file) that should go into the commit. This makes it a lot more easier to manage a large number of changes. Thanks!
  • a
    Can I please get a "None" option here? I don't use shortcuts to navigate and want to minimize risk of losing my spot in a PR because I accidentally click a button
  • s
    This message was deleted.
    e
    d
    • 3
    • 45
  • s
    This message was deleted.
    👍 1
    a
    • 2
    • 1
  • s
    This message was deleted.
    😞 1
    m
    t
    • 3
    • 2
  • s
    This message was deleted.
    ❤️ 1
    j
    • 2
    • 2
  • s
    This message was deleted.
    j
    • 2
    • 1
  • s
    This message was deleted.
    a
    • 2
    • 1
  • j
    Hi everyone - you can now send us feature requests straight from the Graphite web app! To submit, click on "Send feedback" from the help menu in the top right (or use the G > F keyboard shortcut). To eliminate duplicate sources of feedback, we’ll be archiving the #C0164SMAL67 channel, but as always you can search for past feature requests here: https://www.linen.dev/s/graphite/c/feature-requests
  • j
    archived the channel