I’ve tried using git brancheless, git spr and stacked git, but they aren’t sticking in my brain. Does this have a better chance for this interactive rebase and squashed merge user?
Show HN: Graphite – Stacked Diffs on GitHub
41–50 of 65 posts
Re: Show HN: Graphite – Stacked Diffs on GitHub
#42Earlier quoted context omitted.
I think letting me give you a gpg private key and you sign commits with that would be ideal. I'm not sure how the app signing commits would work, since it needs to be signed by a member of our org I believe?
then why not let them generate the key itself?
So I can revoke the key if I need to (my understanding is that you need the private key for that)
Re: Show HN: Graphite – Stacked Diffs on GitHub
#43is this in opposition to trunk based development?
Re: Show HN: Graphite – Stacked Diffs on GitHub
#44Honest question: how did you folks determine your pricing? I totally get that what Graphite offers is valuable and can improve developer productivity. But from where I'm standing, the pricing is disproportionate to the value add.
Github Enterprise - while of course not 1-to-1 comparable - offers so much more functionality for 2/3ds of the cost of Graphite. I'd expect Graphite to cost _less_ than Github Enterprise as it seems it could be positioned more as an add-on to what you get from Github.
Am I missing something?
Re: Show HN: Graphite – Stacked Diffs on GitHub
#45Looks interesting! We already stack PRs by basically having a chain of branches, one on top of each other, that we review separately and merge in order.
What benefit does Graphite provide further?
Main pain point I imagine is dealing with rebases? What else?
Re: Show HN: Graphite – Stacked Diffs on GitHub
#46I've been using Graphite since November 2021 and love it. Aside from stacking, their dashboard is also a huge improvement over Github's.
Re: Show HN: Graphite – Stacked Diffs on GitHub
#47Earlier quoted context omitted.
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)
I think letting me give you a gpg private key and you sign commits with that would be ideal. I'm not sure how the app signing commits would work, since it needs to be signed by a member of our org I believe?
Yep, our app signing the commits would mean requiring your org to approve the app as "someone" who can contribute to the repo
Re: Show HN: Graphite – Stacked Diffs on GitHub
#48Great to see new players in this space. Congrats on the launch!
Re: Show HN: Graphite – Stacked Diffs on GitHub
#49Honest question: how did you folks determine your pricing? I totally get that what Graphite offers is valuable and can improve developer productivity. But from where I'm standing, the pricing is disproportionate to the value add. Github Enterprise - while of course not 1-to-1 comparable - offers so much more functionality for 2/3ds of the cost of Graphite. I'd expect Graphite to cost _less_ than Github Enterprise as…
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 product).
Every single feature of Graphite’s workflow is optimized around stacking, including: - Beautiful code review interface - PR inboxd - Stack-aware merge queue - Team insights - Integration with your favorite tools like Slack and VS Code
Graphite is scalable, and is built for professional software development. Give it a try for free to see for yourself :)
Re: Show HN: Graphite – Stacked Diffs on GitHub
#50Looks interesting! We already stack PRs by basically having a chain of branches, one on top of each other, that we review separately and merge in order. What benefit does Graphite provide further? Main pain point I imagine is dealing with rebases? What else?
Yes, we definitely help deal with the pain around rebasing.
In addition, in our code review interface we provide the ability to see and review PRs in the stack context so reviewers can see and understand what the dependencies are, we have the ability to merge a stack (in full or in part) automating the process of any rebases that need to happen between merges, and we also have a merge queue that is stack-aware which makes sure that PRs added to the merge queue are merged in order while ensuring that everything merged into the main branch has passed tests.
Depending on your org's GitHub settings, using stacks can be a pain because the branch protection rules aren't always clear when you're looking at a PR that is stacked indirectly on a protected branch. In those cases, you may find that as you merge your stack in order, additional blockers get added. Graphite helps to show you these requirements ahead of time so that you can make sure your PRs are actually ready to merge before you start merging.
What are some pain points you or your team face?