Been playing with this as a beta user for a few months. I really like how the cli removes a ton of the footguns I've come to find with git. With Graphite I don't have to think too closely about navigating and reordering branches. It's removed a lot of my fears of "will this command clobber my workspace". The guard rails are up, but you can always drop into git if you need something specific.
Show HN: Graphite – Stacked Diffs on GitHub
61–65 of 65 posts
Re: Show HN: Graphite – Stacked Diffs on GitHub
#62Earlier quoted context omitted.
Hi there, thanks for the question! One quick clarification - the 30 repository limit is per user (not per org), so I expect you would still fall under the Team tier. I'd encourage you to try Graphite out for free - many companies have already found tons of value out of Graphite and are paying for us now. Also - we have a little promo code for users from Hacker News - try out HN15 :)
Thanks for the clarification. The limit of 30 repos per user is indeed more reasonable. The support for Github Enterprise which would necessitate the Enterprise tier, is that referring to all flavors of GH Enterprise or only the on prem version?
Hey DandyDev, our Graphite Free and Team tiers do support our GitHub Enterprise Cloud customers.
If you need GitHub Enterprise Server support (eg. on-prem) then that would require our Graphite Enterprise tier...
Typing this out I realize this is confusing and will reconsider the naming of our tiers.
Re: Show HN: Graphite – Stacked Diffs on GitHub
#63Earlier quoted context omitted.
Thanks for the question! We don't typically compare our pricing to GHE but rather to other similar SaaS tools (check out some merge queue providers - which is just one feature of Graphite). GHE has a very different business model - they keep the per seat price low to charge for compute in CI/CD or upsells into Microsoft Azure. As another counterexample, Superhuman is $30/user/mo for an "add-on" to Gmail (a free produ…
Here's the thing: I think it's a bad idea to try it out, because I can already see in the pricing tiers that if I would like Graphite, I cannot afford it for my team because of the pricing structure. I work for a startup that is less than 3 years old and has ~90 employees of which ~50 are software engineers and data scientists (people writing code). We're VC funded and not profitable yet. When I see a pricing tier ca…
> We also use Github Enterprise (cloud version), which puts us in your Enterprise tier as well.
Why is this at all surprising? If you're using GitHub Enterprise, why wouldn't you be using the Enterprise tier of other software?
Re: Show HN: Graphite – Stacked Diffs on GitHub
#64I'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!
Hey @njaremko, Thank you for using Graphite and your support. This is something we're aware of and current thinking around. Question, if we were to support this by signing commits: Would you want the commit to be signed by the Graphite GitHub App? Or would you prefer for it to be signed by Graphite on behalf of you? Or some other option that we haven't considered? -Xiulung (UX @ Graphite)
Signed locally using your GPG key is the correct answer to this (IMO), otherwise you're replacing a one attestation with a much weaker one.
Re: Show HN: Graphite – Stacked Diffs on GitHub
#65Seems 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.
Hey @juliennakache UX designer at Graphite here, All PRs will be shown with the proper draft/open/closed/merged states on GitHub and on Graphite, we do a lot of work to make sure that the real-time status is synced between the two so that you can adopt Graphite without disrupting your team's existing workflow. Would love to know other pain-points you have around GitHub so that we could make Graphite even better for y…
Hi, sorry just seeing this.
What about the comments on commits? Are those all displayed in the Github PR when it's merged, and attached to all the correct lines, even the ones that were made on branches that were rebased?
Thanks!