Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Git plumbing: Handle errors better #8348

Open
N-o-Z opened this issue Nov 5, 2024 · 2 comments
Open

Git plumbing: Handle errors better #8348

N-o-Z opened this issue Nov 5, 2024 · 2 comments

Comments

@N-o-Z
Copy link
Member

N-o-Z commented Nov 5, 2024

We rely on git command output message to translate it into meaningful errors. This might become tricky in some scenarios:
#8345 (review)

@talSofer
Copy link
Contributor

This can be prioritized as a tech debt, removing from the product backlog

@yonipeleg33
Copy link
Contributor

It might be worth looking into formatting the git command output in a machine-readable way.
For example, commands like git status has the --porcelain flag, other commands like git log have the --format flag, and there are other helpful flags out there.

I've chatted about it with Perplexity, it might contain interesting information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants