Skip to content

spr stack trace on every "normal" error can be confusing #512

Description

@astutecat

Hi!

Thanks for making such a neat tool to do stacked PRs. I'm really enjoying using it.

One thing that is confusing though is that there is often a stacktrace that gets printed out when a git command (for example) fails "normally" -- for example, if I don't stage any files before running git spr amend.

In this situation, it seems the stack trace isn't really helpful since there isn't a bug in spr, and the information message I really need to read is the output from the git command, which gets pushed up by the stack trace.

Would there be a way for this to not output a stack trace, and print it when supplying the --verbose flag? Or, failing that, can I have it so that I can suppress the stack traces with an environment variable?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions