You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just saw #87, which I did not in my initial basic search about "commit message" or whatever.
Feel free to close this one, although has images for reference.
About complexity (and unforeseen required necessities) VS utility tradeoff, totally understandable.
I might end up using the UNDO command and editing it there anyway out of habit.
Yup, and it's good to have an issue for this now. {COMMIT_MESSAGE} would be the way to go, but the thing is the full message is not available, it's only fetched on demand for the commit detail view. So we'll need some logic that detects the COMMIT_MESSAGE and when it's there, will query for it, before the git action can be executed (but already modified). And then it'll still have to be loaded for the commit details view because the two logic pieces don't have anything in common, really. so maybe some sort of commit message cache.. yeah that's why I haven't done it so far.
Would be nice to get the message your are going to edit as placeholder instead of a general one:
For example when I undo a commit with the vscode "Git: Undo Last Commit" I get the commit message used:
For comparison the edit branch name does provide the previous name as placeholder:
Regards
The text was updated successfully, but these errors were encountered: