GitHub going sideways for anyone else? We keep getting 404's

anyone else having issues using homebrew to install graphite-cli ?

╰─ brew install withgraphite/tap/graphite
==> Tapping withgraphite/tap
Cloning into '/opt/homebrew/Library/Taps/withgraphite/homebrew-tap'...
fatal: invalid branch name: init.defaultBranch = 
Error: Failure while executing; `git clone <https://github.com/withgraphite/homebrew-tap> /opt/homebrew/Library/Taps/withgraphite/homebrew-tap --origin=origin --template= --config core.fsmonitor=false` exited with 128.

Do you guys support startups? Are there any startup package that I can apply?

Hello there, what does it mean when a pull request is "Waiting on downstack"? And how can I change that state? I can't find the information in the documentation.

Do we have any rewards for early adopters?

how invite others people join the channel

Curious if Graphite has an affiliate program? I'm going to start youtubing /streaming, I use graphite in my workflow and feel like it would be a really natural way to introduce people to the stacked workflow. More specifically,

Sign up to graphite with my promo code and get x months off / discount whatever

Hi! just wondering what the definition of “active stack” is? I know it’s at least 2 branches in a stack, but does it only count if those branches are not yet pushed to remote? We just got the warning that we have used 7 out of 10 stacks in our organization, but based on our PRs (both open/in draft), I only count 4? Is there a way to see what stacks exist?

Does anyone have the graphite fractal and graphite images? I would love to upload them to my teams S slack channel so I can slowly convert the team.

Heard good things 👍

Alright converted another eng to graphite fractal party parrot

Any advice for troubleshooting high memory usage and crashes in the web app? Is it just something weird with my setup or 🤔

Thank you so much for fixing the bug which always reset the dashboard to the top when navigating back! ❤️

has anyone ran benchmarks on how arc compares to chrome in terms of battery consumption?

is graphite ready to run on node 20?

i see this process eating my CPU, what is it?

node ~/.local/share/nvm/v18.8.2/bin/gt background feature-flags

We are HERE at re:Invent, let us know in this thread if you’re here and come say hi!! Also if you see any of stickers secretly placed around the conf snap a pic and share it with us here or on twitter @withgraphite 🫵😎📸

👋 Graphite users often tell us that they'll document how to use Graphite on an internal wiki/Google Docs/Notion and share it out with their team. if anyone is willing to share said document(s) with me, would you DM me or email db@graphite.dev? feel free to redact anything that needs redacting of course! my goal: learn about the kinds of tips & workflows you find important to share, and then write this guide once on graphite.dev so you can all stop writing it N times 🙂

👋 Hello! I’m working on making Graphite friendlier to new users. I’d love to interview anyone on your team next week that either: • Has tried to use Graphite before, but bounced • Knows about Graphite, but hasn’t gotten around to trying it yet • Is a power user that encourages the rest of the team to use Graphite If you're interested or know someone who would be a good candidate, please use Calendly to schedule 15mins with me 🙂 : https://calendly.com/david-balatero-graphite/user-interviews

This is a first! Very cool

I was unaware of the fork limitation, and created 6 PRs against my fork. I want to now create the stack against the upstream, and have renamed my remotes accordingly -

origin

(fork) is now

fork

,

upstream

is now

origin

. But now

gt stack submit

refuses to do anything:

✏️  Preparing to submit PRs for the following branches...
▸ friel/docker (No-op)
▸ friel/docker-sec (No-op)
▸ friel/ssm-params (No-op)
▸ friel/init-index (No-op)
▸ friel/parameterize-sql (No-op)
▸ friel/pulumi-config (No-op)

Now I'm not sure how to reset Graphite and make it forget about these PRs on the fork. I've closed all of those, as you can see here: https://github.com/AaronFriel/aws-reference-architecture-pulumi/pulls?q=is%3Apr+is%3Aclosed So, really hard to figure out exactly what to do now.

Ah,

gt init --reset

seems to be the thing to do.

🚨 New blog post hot off the presses!! Read all about why we use AWS ECS instead of Vercel to host Graphite! https://graphite.dev/blog/why-we-use-aws-instead-of-vercel

Could someone give me a quick overview of the differences between the Github Merge Queue and Graphite Merge Queue? Is the main value add of Graphite's Merge Queue the optimizations for stack merges? Are there things that would break in Graphite usage (on a team where some devs use Graphite and some use Github) if we enabled the Github MQ?

Am I hallucinating or did "stack test" go away?

Am I missing something fundamental here or do I really need to either manually re-target the next PR or do a

gt sync

then

gt submit

every time after I merge the bottom of a stack? I expected to be able to go to the bottom of a stack in the app, give one last look over, merge it, then repeat for the next in the stack and so on.

The troubleshooting page still has some old commands on it. For example, it suggests

gt repo init --reset

, to which the CLI responds > WARNING: This command has been renamed and will be fully removed soon. Please use gt init instead. https://graphite.dev/docs/troubleshooting

https://github.com/withgraphite/graphite-cli/blob/main/README.md says:

we will be developing v1.0 of the Graphite CLI within our monorepo and leaving the public repository archived as an artifact

but doesn't provide a hyperlink. NPM still points to https://github.com/withgraphite/graphite-cli Question) • where is the monorepo?

Hello Everyone I am new to Graphite can any tell me what i can use this tool for in a simple sentence or give me a use case to better understand what it does and how i can leverage on it> Thanks

Happy Wednesday friends. Just wanted to give a quick update on something that's been top of mind here at Graphite recently: Merge Queue. We've heard your feedback around some pain points when using the Graphite MQ with your team and with external mq's. What we've done so far: • New error messages - previously the Merge Queue could be unclear why your PR would fail to merge • Auto-comment on PR's in orgs where Merge Queue is enabled to add visibility ◦ Allows for easier interoperability/enforcement with non-Graphite users. ◦ Everyone using Graphite MQ gives you one place to manage your merges. ◦ It's easier to keep your merges in-order (and main green) from GitHub. ◦ Documentation What we're planning on doing: • New Merge Queue settings page ◦ Better UX ◦ Better messaging and visibility into MQ behavior ◦ Centralized visibility into all Merge Queues across all your repos We want your feedback! 🫵 If you're currently using the merge queue we'd love to have more feedback around the experience as we continuously work to improve it. If you're not using the merge queue yet, even better! We'd love a fresh set of eyes on it. • DM me! • Email support@graphite.dev • Post in this 🧵 Thank you!!