krauterbaquette/sac
3
1
Fork 0
Code Issues 2 Pull requests Projects Releases Activity Actions

Better default message for merge sync #19

New issue
Open
opened 2025-01-01 02:26:08 +00:00 by krauterbaquette · 0 comments
krauterbaquette commented 2025-01-01 02:26:08 +00:00
Owner
Copy link

When executing sac sync after resolving merge conflicts,
the commit message should not be edited (if no commit message is specified).

Due to debasing, no merge commit will be created, but the first commit with a conflict will be overwritten. Therefore most of the time one wants to keep the original commit message

When executing `sac sync` after resolving merge conflicts, the commit message should not be edited (if no commit message is specified). Due to debasing, no merge commit will be created, but the first commit with a conflict will be overwritten. Therefore most of the time one wants to keep the original commit message
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
cmd-log
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
krauterbaquette/sac#19
No description provided.