-
Notifications
You must be signed in to change notification settings - Fork 346
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
Avoid using same command for querying and mutating (e.g. branches) #330
Comments
arxanas
added a commit
to arxanas/jj
that referenced
this issue
May 28, 2022
arxanas
added a commit
to arxanas/jj
that referenced
this issue
Jun 3, 2022
arxanas
added a commit
to arxanas/jj
that referenced
this issue
Jun 6, 2022
arxanas
added a commit
to arxanas/jj
that referenced
this issue
Jun 6, 2022
arxanas
added a commit
to arxanas/jj
that referenced
this issue
Jun 6, 2022
arxanas
added a commit
to arxanas/jj
that referenced
this issue
Jun 6, 2022
martinvonz
pushed a commit
that referenced
this issue
Jun 6, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
@arxanas shared this confusing snippet:
I agree that that behavior is confusing. Git and Mercurial behave the same way. However, in their defense, they don't have subcommands at all, so the user is much less likely to think that using
branch delete
for deleting a branch would work. Since we do have subcommands, we may want to use them more consistently and never (?) have the same command either query or mutate the repo (except for the automatic working copy snapshots) depending on arguments.@arxanas suggested having
branch create
,branch delete
, andbranch list
(replacing the currentbranches
). That sounds good to me, but I'm happy to hear what others think.Specifications
The text was updated successfully, but these errors were encountered: