-
Notifications
You must be signed in to change notification settings - Fork 1.3k
exp list: add the new flags (including -A/--all-commits) (#7153) #7245
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
Conversation
4996a9c to
ce68fea
Compare
3f93209 to
4ccc0ce
Compare
9c5b39e to
338b4e6
Compare
pmrowla
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will need a docs PR.
@karajan1001 it would also be helpful to put together an asciinema demo of the new flags (it would be fine to have one demo containing all of the different commands instead of a separate demo for each of these PRs)
9e1a4f1 to
20ef402
Compare
dvc/commands/experiments/__init__.py
Outdated
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, I have a question: what happens when --rev (or an included parent) is a merge? Which <num> ancestors are included?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It will include the first parent for merge commits (linear ancestors, equivalent to using tilde ~ in git). We don't support specifying a different parent (i.e carat ^ in git).
So for --rev HEAD -n 2 You would get the commit referenced by HEAD~2 in git (as opposed to HEAD~2^2/HEAD~2^3...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it, thanks @pmrowla ! I wonder if we want to include this info. in the description or in docs. May be relevant if people use large -n values (likely to include merges) cc @karajan1001 .
|
@karajan1001 What's the status of this one? Seems like this one needs to be merged before moving forward with the related core and docs PRs. |
|
@jorgeorpinel, Need some final check and approval. the other two one #7275, #7255 all depend on it. |
|
@karajan1001 I still see that |
need to release a new version. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Output strings look good, thanks.
fix: treeverse#7153 Unify the flags in `exp list` to `exp show` 1. Add new `-A`, `-n` flags to `exp list` command. 2. Add unit test for the flag parse. 3. unify the revs retrive logic to `exp show`. 4. Add functional test for `exp list` 5. Update the documents. Co-authored-by: Jorge Orpinel <jorgeorpinel@users.noreply.github.com>
) * add a new `num` arg to exp list, rename `--all` to `--all-commits` Related to treeverse/dvc#7245 * Some updates * Update content/docs/command-reference/exp/list.md Co-authored-by: Jorge Orpinel <jorgeorpinel@users.noreply.github.com> * Restyled by prettier Co-authored-by: Jorge Orpinel <jorgeorpinel@users.noreply.github.com> Co-authored-by: Restyled.io <commits@restyled.io>
) * add a new `num` arg to exp list, rename `--all` to `--all-commits` Related to treeverse/dvc#7245 * Some updates * Update content/docs/command-reference/exp/list.md Co-authored-by: Jorge Orpinel <jorgeorpinel@users.noreply.github.com> * Restyled by prettier Co-authored-by: Jorge Orpinel <jorgeorpinel@users.noreply.github.com> Co-authored-by: Restyled.io <commits@restyled.io>
fix: #7153
Unify the flags in
exp listtoexp show(including -A/--all-commits)
Wait #7152 and #7206
-A,-nflags toexp listcommand.exp show.exp list❗ I have followed the Contributing to DVC checklist.
📖 If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏