A version workflow would be useful, especially for less technical users. Additionally, whenever I am faced with a new command I reasonably expect $CMD [--help|help] and $CMD [--version|version] to work.
Details
Details
- Reviewers
epriestley - Group Reviewers
Blessed Reviewers - Commits
- rARCb7bb6c834830: Add a `version` workflow to arcanist.
Ran arc version.
Diff Detail
Diff Detail
- Repository
- rARC Arcanist
- Lint
Lint Skipped - Unit
Tests Skipped
Event Timeline
Comment Actions
See D9267, mostly.
Otherwise, if any of the paths are not git working copies or the git binary is not available on the system, we should recover gracefully. arc upgrade has a check for the former, although both workflows should probably check both.
Comment Actions
- Simplify logic for determining the commit timestamp.
- Fail gracefully if git is missing.
- Fail gracefully if the .git directory does not exist.
Comment Actions
This is what the output looks like:
> arc version arcanist 635f49dc5466979d2ddef02269c512c2aff912c2 (24 May 2014) libphutil 1add454ccdb7a23bd8d1823452c570bf2ae445e0 (19 May 2014)
Comment Actions
Closed by commit rARCb7bb6c834830 (authored by @joshuaspence, committed by @epriestley).