Yuya Nishihara f9906dc403 cli: add "git.push-new-bookmarks" config knob to enable --allow-new by default ... This goes against our rule that we shouldn't add config knob that changes the command behavior, but I don't have any other idea to work around the problem. Apparently, there are two parties, one who always wants to push new bookmarks, and the other who mildly prefers to push&track new bookmarks explicitly. Perhaps, for the former, creation of bookmarks means that the target branches are marked to be pushed. The added flag is a simple boolean. "non-tracking-only" behavior #5173 could be implemented, but I don't want to complicate things. It's a failed attempt to address the issue without introducing config knob. Closes #5094 Closes #5173		2025-01-15 07:23:43 +00:00
..
examples	examples: use settings_for_new_workspace() when initializing workspace	2025-01-06 21:15:28 +09:00
src	cli: add "git.push-new-bookmarks" config knob to enable --allow-new by default	2025-01-15 07:23:43 +00:00
testing	merge_tools: add "$marker_length" variable	2024-12-23 08:42:10 -06:00
tests	cli: add "git.push-new-bookmarks" config knob to enable --allow-new by default	2025-01-15 07:23:43 +00:00
build.rs
Cargo.toml	cargo: remove minus dependency	2025-01-14 01:13:13 +00:00
docs
LICENSE