Ref T5781. This makes things like arc browse master work (but they open the commit, not a revision).
Details
- Reviewers
btrahan csilvers - Maniphest Tasks
- T5781: Moar functionality for `arc browse`!
- Commits
- rARC26b71baf0919: Allow "arc browse <symbol>" to resolve symbolic commits
Ran arc browse master.
Diff Detail
- Repository
- rARC Arcanist
- Branch
- browse4
- Lint
Lint Passed Severity Location Code Message Advice src/repository/api/ArcanistSubversionAPI.php:217 XHP16 TODO Comment - Unit
Tests Passed - Build Status
Buildable 2035 Build 2036: [Placeholder Plan] Wait for 30 Seconds
Event Timeline
I'm not sure I understand when you use plural arguments -- does that mean you can do arc browse D1234 T5678? If so, am I reading the current review right that it will either interpret all arguments as commits, or all arguments as objects, or all arguments as files? I'm probably not.
You can specify multiple objects, yes. We try to resolve them in this order:
- object names (like T123).
- if you're in a working copy:
- symbolic commits.
- paths which exist in the working copy.
- (with --force: force everything that's left to resolve as a path).
They fall through if they fail an earlier resolution:
$ arc browse T234 master README Opening T234 as an object. Opening master as a commit. Opening README as a repository path. $
(There's no way to force T123 to resolve as a symbolic commit or a path, nor to force master to resolve as a path, but I suspect no one will ever care, and we could introduce some --path flag if they do.)
Oh, I think i was just misundersatnding how the php works. I see the unset commands now, and the logic makes more sense to me. But clearly I am not the best person to be reviewing this...