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

cli: add "git.push-new-bookmarks" config knob to enable --allow-new by default #5358

Merged
merged 1 commit into from
Jan 15, 2025

Conversation

yuja
Copy link
Contributor

@yuja yuja commented Jan 14, 2025

#5094

Checklist

If applicable:

  • I have updated CHANGELOG.md
  • I have updated the documentation (README.md, docs/, demos/)
  • I have updated the config schema (cli/src/config-schema.json)
  • I have added tests to cover my changes

…y 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 jj-vcs#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 jj-vcs#5094
Closes jj-vcs#5173
@yuja yuja added this pull request to the merge queue Jan 15, 2025
Merged via the queue into jj-vcs:main with commit f9906dc Jan 15, 2025
19 checks passed
@yuja yuja deleted the push-zvlrzrnnxqtk branch January 15, 2025 07:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants