Hi everyone, and thank you for making such great tool. The tool is great but there was some rough edges around payments and campaigns, I wanted to ask about in here. Last year Graphite had announcement that you guys giving a free Standard plan for small teams, i.e. teams with less than 10 people. Exact words were:

Completely free for companies, personal projects, and individuals with fewer than 10 collaborators on GitHub. We understand that every big company starts as a small company, and we want to support you every step of the way. Just email support@graphite.dev with your org name and we’ll set you up.

Our company (5 devs) did qualified for a definition of a "small company", so we've contacted the support and they have set us up. Then, in the Billing page, Standard plan has appeared and activated, with a coupon code applied, and the label said the coupon code will expire in one year, and after that it will be ~1000$ per year. I've contacted you guys about the fact that in the announcement there was not a word about expiration. Thats why we've applied to the plan in the first place. Then Joyce (@Joyce Lu , I believe) from the support replied:

I believe the coupon will renew after 1 year if you still qualify for the free Standard plan 🙂

That seemed super nice, and everyone lived happily ever after. Until our credit card was charged for 990 USD couple days ago, exactly one year after, without any notifications about whether we are still qualified for the definition of "small company" or not. That was quite unexpected. We are still 5 devs company by the way. I've asked Joyce by email, but that was 3 days ago, still no reply... So I decided to ask that here. Best regards.

Curious what ai model the AI Code Review feature uses. Anybody know?

hi team - accidentally subscribed to the wrong plan

just did it a few seconds ago, who can i speak to to get this adjusted?

How do you qualify for startup?

Graphite reviewer actually been very helpful. Best AI reviewer product i've used so far.

Building on ^^, sharing something really cool: Graphite Reviewer just corrected the error handling from an HTTP request, based on the actual hash returned in the response value. It did that because we cache and replay external requests in our test suite using VCR. It’s a very unexpected benefit that Graphite will now validate our response handling.

The error handling assumes

error['type']

exists, but based on the API response format shown in the VCR cassette,

finishReason

appears to be a string (e.g.

"STOP"

), not a hash. This will cause a NoMethodError when trying to access

error['type']

. Consider handling both string and hash error formats, or update the code to match the actual API response structure.

Any graphite presence at reinvent?

Good evening, may I ask if the Graphite Reviewer 30 days trial is separate from the regular 30 days trial? My team would love to try this but we have not gained approval for purchasing the additional license for the AI reviewer.

I just saw the following on Graphites pricing page. And I am getting flashbacks because this looks like you are going to take away the analysis features from the base plan and move them in a paid addon tier. We don't use it much, but this is the third feature which was part of Graphite when we made the decision to use graphite and which has, since then, been taken away from us. You want to let people pay for extra features? Fine, no problem. But I feel like you are slowly taking away features, one after another. Graphite Core is already quite expensive. Compare 20$/contributer/month with e.g. GitHub. GitHub Team is 4$/contributer/month but does all the heavy lifting and is the much more critical component compared to graphite. I am fine with paying premium prices on premium features, but recently Graphite got more and more unstable from what it was when we started using the product + more and more features were taken away from us (automations first, then CI optimizations, now Analyis). At what point will this stop and when is there a turnaround in how things are developing? When can I expect a certain core functionality to stay in the 20$ pricing tier + stay stable?

Hello, I couldn't find any docs on graphite's code retention policy and deletion of a company's code. Please help 🙏

where can I find a reference for the keyboard shortcuts?

are there any alternatives to graphite that work on gitlab? i had a look at gitlab stacked branches, but it seems to be lacking in functionality.

Hey team, I love using the version diff mode to see code changes I've made since the last push, but the comments since then tend to get in the way. Is there a way to hide the comments?

I have what may be a stupid question. Say I have a stack submitted, with featA based on main, and featB based on featA. There is no overlap in what lines featA and featB modify. If I change featA, then when I sync the stack, it also needs to force push and update featB. Is this strictly necessary, or would the merges ultimately be fine without updating featB since the diff of featB to featA is unchanged?

Does anyone else feel the Graphite Slack add on notifications are not quite up to date? I usually experience delays ranging from a few minutes to several hours, especially for PR approving.

Anyone have advice on how to "sell" Graphite to your team/decision makers. I think I was terrible at maybe showcasing it as this is the response I got back ha.

FYI: https://www.producthunt.com/p/graphite/you-re-doing-code-reviews-wrong-ama-w-ceo-of-graphite-hey-product-hunt

-- Telescope picker for files in most recent git commit
local pickers = require 'telescope.pickers'
local finders = require 'telescope.finders'
local conf = require('telescope.config').values
local Job = require 'plenary.job'
local function git_last_commit_files()
  ---false alarm warning
  ---@diagnostic disable-next-line: missing-fields
  Job:new({
    command = 'git',
    args = { 'diff-tree', '--no-commit-id', '--name-only', '-r', 'HEAD' },
    on_exit = function(j)
      local results = j:result()
                                                                                                               
      vim.schedule(function()
        pickers
          .new({}, {
            prompt_title = 'Files in Last Commit',
            finder = finders.new_table { results = results },
            sorter = conf.generic_sorter {},
            previewer = conf.file_previewer {},
          })
          :find()
      end)
    end,
  }):start()
end
vim.keymap.set('n', '<leader>sc', git_last_commit_files, { desc = '[S]earch [c]hanged files in last commit' })

Neovim telescope picker for only choosing from your most recent commit's files. Handy for working in a Graphite stack.

Not really product related, but does anyone know what the Diamond reviewer logo is supposed to be? I’m not able to interpret anything from it lol

Can we bump up the number of tracked repos from 30 to something else? Our team has comfortably hit the limit.

Anyone elses auth not working this morning? I can't seem to push using graphite and creating new tokens isn't work for me either

Don't have a great place to share this, so #C02MWL10SR0 it goes: ⚠️

SPAM

— Someone is advertising their product via DMs in this Slack

this is such a cool feature — this line I was pointing at was in fact removed in that upstack PR. chefs kiss

Hi 🙂 Not sure where to ask - I'd like, when setting a full stack of PRs to merge when ready, that the merge (more accurate - the rebase after the merge) won't trigger the CI all the way to the top of the stack. If I try to merge a stack of 10 PRs that's

((10+1) choose 2) = 11*10/2 = 55

CI runs for a fully ready stack of 10 PRs. Is this something that can be done?

I keep accidentally losing big

gt split

operations after like 5 mins of careful work by accidentally pressing escape (vim habits) 😢

whoever came up with the copy on this button was absolutely cooking

accidentally just requested to install Claude for this Slack instead of my personal Slack ... it had a lightly humorous message. sorry, Slack admins. ignore 😅

I would like to confirm how to check whether the onboarding process has been completed. As far as I understand, if all 5 team members complete the onboarding, an additional 30 days will be granted. Could you kindly let me know how I can verify whether all members have completed their onboarding?

If you ever wondered how many PRs graphite can handle in a stack, the answer is that you can have many, but after 50 or so the web UI will be somewhat slow 😃