2 ms·
> It provides a consistent naming of command. Very nice. > Gut also prevents you from shooting yourself. Excellent. > Finally, git was made when GitHub and
by yjftsjthsd-h 4y ago
> It provides a consistent naming of command.
Very nice.
> Gut also prevents you from shooting yourself.
Excellent.
> Finally, git was made when GitHub and others didn’t existed yet. To diff commits, gut opens the compare view in the browser. And to merge a branch, gut opens a pull request.
Eh... here you start to lose me. A lot of my repositories get pushed to a personal server (which for me personally is usually just a bare repo, but could be ex. gitea). On the hosted side, I use GitHub and GitLab, which you do support, but I also use sourcehut.
Finally, the telemetry is a big red flag for me. Opt-out is always a red flag, especially since you don't appear to signal it to the user up front. And under things collected at https://gut-cli.dev/docs/#64dc74dd-8a3d-44d6-aab7-55483519a853 https://gut-cli.dev/docs/#64dc74dd-8a3d-44d6-aab7-55483519a8... , what exactly does
> The command you used
mean? Just which function is being called, or arguments as well? Because I would very much like to not be sharing things like branch names with a third party.
- julien040 4y agoHi, I am considering removing telemetry because it appears to be a major issue. When Gut is launched for the first time, it collects consent and the user can opt-out at any time by running "gut telemetry disable". Arguments are not logged. Here is an example of what the data looks like in BigQuery: https://cln.sh/PRcGwd6M https://cln.sh/PRcGwd6M
- yjftsjthsd-h 4y ago> When Gut is launched for the first time, it collects consent Meaning it asks the user whether it may upload telemetry, yes or no? Because that would be fine, though I would think less of it for defaulting to yes.
- julien040 4y agoYes, it asks if telemetry can be enabled. Here is how it looks: https://cln.sh/rCmVtVhZ https://cln.sh/rCmVtVhZ