2 ms·
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
by timvdalen 3y ago
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.
- kdottt 3y agoHey Tim! Thanks for being with us since the beta. Would love to help you walk through that git query issue. Might be easier on our community slack if you wanna come chat about it there! https://join.slack.com/t/graphite-community/shared_invite/zt-v828g9dz-TIRvlutxTCqgZmxnsO9Knw https://join.slack.com/t/graphite-community/shared_invite/zt...
- timvdalen 3y agoWill drop a line the next time I hit it!
- jacobegold 3y agoSo 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.
- timvdalen 3y agoWill 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.