This message was deleted.
# feature-requests
s
This message was deleted.
👀 1
3
b
These comments are part of why I don't merge via the Graphite interface. They don't carry unique information, and come across as just trying to get a link to "Graphite" in front of more people (at our cost by lowering the signal/noise ratio). By contrast, the Graphite comments that show the stack info are wonderful cause they carry unique and useful information.
3
k
thank you for this feedback! for context, we built these comments to let you know what's happening with your merge but y'all are right that this is only really useful to the author -- we'll explore ways to make this less noisy and more actionable 🙂
❤️ 1
a side note~ as a workaround for now, graphite slack notifications will ignore these comments!
b
BTW, I'm not actually accusing y'all of growth hacking 😬 . I'm just sharing the feeling that non-Graphite users on my team have had around things like this. Thank you all for always being receptive 🙂
🎯 1
🙏 1
j
The reason we added these is to keep visibility high for what the jobs that we run are doing — especially the rebase one — we were concerned that folks would be concerned by the opaque "force pushed this branch" comment, and the rationale behind the merge one is that without it, it looks like the user themself pressed merge on GH (not that it was done by an external application).
a
Both reasons make total sense for getting started with Graphite but using it heavily and merging multiple branches a day it becomes annoying. Our entire team uses Graphite and we don't care which tool someone used to merge or rebase a branch. We trust each other and for that reason it seems unnecessary to us.
1
b
Maybe this can be a setting, defaulting either way.
👍 1
j
It should be easy enough for us to add a setting here. I think that's the first change we'll make!
❤️ 4