3 ms·
I know you're trying to avoid footguns - but how do you handle workflows where up-to-date rebases are required? Several repos I've been in ask for commits to be
by nidnogg 4y ago
I know you're trying to avoid footguns - but how do you handle workflows where up-to-date rebases are required? Several repos I've been in ask for commits to be rebased to the latest branch for new changes to be PR'd in, and those require the `-f` flag after rebasing to rewrite the local history AFAIK.
Also I'm not too sure about the default opted-in telemetry, I definitely believe a prompt on install would be better in its stead.
Otherwise this looks like a cool project, not something I'd use but very neatly made. Kudos to pulling this off on your first year of CS!
- julien040 4y agoHonestly, some workflows seem complex and I don't think I have the necessary experience to handle them. I think this case falls under "gut can't handle that and you must use git". Regarding the telemetry, it is not opt-in by default. On the first launch, the CLI asks if the telemetry can be enabled. Here is how it looks: https://cln.sh/rCmVtVhZ https://cln.sh/rCmVtVhZ
- wadadadad 4y agoConsider editing the docs to state that telemetry is not enabled by default; I'm more interested in software that respects privacy and adding that to the docs would be a positive for me. https://gut-cli.dev/docs#9351504d-284d-4e59-81a1-465835682b33 https://gut-cli.dev/docs#9351504d-284d-4e59-81a1-465835682b3... Additionally, consider removing telemetry data after a period of time for added privacy.
- julien040 4y agoI've added this to the docs. Thank you for pointing this out