Live data from Hacker News

Show HN: Graphite – Stacked Diffs on GitHub

news.ycombinator.com

11–20 of 65 posts

Re: Show HN: Graphite – Stacked Diffs on GitHub

#11

I’ve tired the CLI, but couldn’t get into it. I’ll have to try the VSCode extension and give it another shot

Jacob and Alyssa on the team have been working hard iterating rapidly on the VSCode to make a more convenient and intuitive way to stack changes. Please send us any feedback you have through our site or the community slack, would love to hear your thoughts!

Re: Show HN: Graphite – Stacked Diffs on GitHub

#14
I've been using this for a few months now, and it's been an absolute joy to use.

One thing that's been a bit annoying: my org enforces signed commits, and when you merge a stack, they sometimes rebase commits internally and lose the code signing, so you end up with an error to merge the rest of the stack.

Aside from that, working with stacks has been great!

Re: Show HN: Graphite – Stacked Diffs on GitHub

#15

I've been using Graphite for a few months now (yay, finally works on cygwin!), and I've been really enjoying it. The command name change will take some time to get used to, though! I've run into a bug with 1.0 where it tries to query git for an object (something with ^tree) that it doesn't understand. I think I'm on a high enough git version, but that could be my issue.

So sorry about that! If you update to the latest version of v1, we added a check to verify your Git version is up to date -- we use a feature from v2.38. Reach out to me (Jacob Gold) on our Slack Community if you're still seeing this issue. The link's on the Graphite website.

Will do!

While I'm at it, will there be a setting to automatically delete branches after merging (on app.graphite.dev)? Without manually deleting all branches after a merge, `repo sync` (or just `sync` now, I suppose!) doesn't pick up that a branch has been merged.

Re: Show HN: Graphite – Stacked Diffs on GitHub

#17
Seems interesting! I've been very unhappy with Github workflow and UI for PRs. It's insane that each time you rebase a PR, you lose all your existing comments on that PR (i.e. they are no longer attached to lines in the UI).

Does anyone know if you need Graphite to see a PR once it's been merged in the Github repo? I'm curious about how locked you in when you start using Graphite.

Re: Show HN: Graphite – Stacked Diffs on GitHub

#18

Seems interesting! I've been very unhappy with Github workflow and UI for PRs. It's insane that each time you rebase a PR, you lose all your existing comments on that PR (i.e. they are no longer attached to lines in the UI). Does anyone know if you need Graphite to see a PR once it's been merged in the Github repo? I'm curious about how locked you in when you start using Graphite.

Not locked in at all!

Graphite syncs bidirectionally with GitHub so that you can see the same information in realtime across platforms. This also means you can use Graphite even if the rest of your team isn't yet!

Post reply on HN