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

Add git commit hash to CLI output #201

Open
1 task
hu55a1n1 opened this issue Sep 12, 2024 · 2 comments
Open
1 task

Add git commit hash to CLI output #201

hu55a1n1 opened this issue Sep 12, 2024 · 2 comments
Assignees
Labels
devx Issues related to improving dev experience / tooling quartz-cli
Milestone

Comments

@hu55a1n1
Copy link
Member

Summary

Print the git commit hash in the description. This makes it easier to identify the exact source that was used to create the CLI binary and will help us in debugging user/dev issues in the future.

Acceptance Criteria

  • The git commit hash must appear on stderr for all CLI commands.
@hu55a1n1 hu55a1n1 added devx Issues related to improving dev experience / tooling quartz-cli labels Sep 12, 2024
@dusterbloom dusterbloom self-assigned this Sep 13, 2024
@dusterbloom
Copy link
Contributor

@hu55a1n1 do we prefer the long or the short hash?

@hu55a1n1
Copy link
Member Author

This is what I had in mind -> <pkg-version>+<git-branch>-<git commit hash (short)>, e.g. 0.1.0+hot_fix_branch-760270a8-dirty. Here's the PR where we implemented this for hermes -> informalsystems/hermes#1101
Also would be nice to display just the version if quartz was installed using cargo install (i.e. the public release).

@ebuchman ebuchman added this to the Next Release milestone Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devx Issues related to improving dev experience / tooling quartz-cli
Projects
None yet
Development

No branches or pull requests

3 participants