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

bookmarks: Make target revision a required argument to create/move/set #5527

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

drieber
Copy link

@drieber drieber commented Jan 30, 2025

This change is not backwards compatible, but it should be very easy to adapt to it.

This fixes
#5374
See also
#5363

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

Copy link
Contributor

@yuja yuja left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks.

cli/src/commands/bookmark/create.rs Outdated Show resolved Hide resolved
cli/tests/test_git_fetch.rs~ Outdated Show resolved Hide resolved
@drieber drieber force-pushed the push-vqwusvyuutsl branch 2 times, most recently from aff9a32 to b4610d5 Compare January 31, 2025 19:02
…e/move/set.

This change is not backwards compatible, but it should be very easy to adapt to it.

This fixes
#5374
See also
#5363
@arxanas
Copy link
Contributor

arxanas commented Jan 31, 2025

Should we make this a soft deprecation in the next version and a hard error in the subsequent version? It seems like it might break real interactive and non-interactive workflows in a frustrating way. It looks like the hard work of migrating all the tests is already done, so hopefully it's a small additional change?

@PhilipMetzger
Copy link
Contributor

Should we make this a soft deprecation in the next version and a hard error in the subsequent version? It seems like it might break real interactive and non-interactive workflows in a frustrating way

yes, that should be done and actually deprecated after 6 releases, like the rest of the user-visible command changes.

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.

4 participants