-
-
Notifications
You must be signed in to change notification settings - Fork 136
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
More informative commit view #488
Comments
Would this option suffice? |
I think full diff is too much I also like to see a summary of things that are being commited. |
In #492, @tomngo asked for previous commit messages, since commit messages will often be similar. Let's come up with all the possible bits of information we might want in the commit view, and then expose a config option to allow people to set this up granularly. One way would be to just accept a raw However, this would be more heavy-handed, and exposing more constrained but popular choices as boolean options might be better. Thoughts? |
Thanks! For convenience, I'd prefer the more constrained but popular choices. If there were a way to enhance by adding raw |
I'd really like this improvement. One thing that wasn't mentioned is showing the branch we are on. I'd like that too. |
Ability to select previous commit messages would also sort-of solve #503. |
@tomngo could you elaborate on what you mean by "'enhancing by adding raw Today, you could either enhance specific GitSavvy commands with custom arguments globally, or define a custom command to do your specialized work. Please let us know if this is satisfactory, and whether there's anything else you're looking for. |
@asfaltboy : My comment was a response to @divmain 's question on the same day (Aug 10). I think your "define a custom command" response already satisfies the need. Thanks! |
Thanx. |
When im writing commit message I prefer to see changes that will be commited and branch info.
Now it looks like:
But view like this looks more informative:
Suggest extend commit view with extra information
The text was updated successfully, but these errors were encountered: