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

CLI: add version command #32

Merged
merged 3 commits into from
Apr 6, 2020
Merged

CLI: add version command #32

merged 3 commits into from
Apr 6, 2020

Conversation

tri-adam
Copy link
Member

Improve Magefile versioning. Add version command, which displays client and service version information. Fix panic in setUserAgent() when nil http.Transport used.

@tri-adam tri-adam marked this pull request as ready for review April 6, 2020 13:42
Copy link
Member

@dtrudg dtrudg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code reads 👍 to me, and tested working with some tags.

I have a couple of minor thoughts which are really probably feature requests, and can be deferred.

  • Would be nice to have the magefile.go report a warning if a tag object is not found, as someone is, at some point going to tag without -a and wonder why everything is unknown.
  • Would be nice to have the git commit set even if there is no tag and version is unknown.

@tri-adam
Copy link
Member Author

tri-adam commented Apr 6, 2020

Code reads 👍 to me, and tested working with some tags.

I have a couple of minor thoughts which are really probably feature requests, and can be deferred.

  • Would be nice to have the magefile.go report a warning if a tag object is not found, as someone is, at some point going to tag without -a and wonder why everything is unknown.
  • Would be nice to have the git commit set even if there is no tag and version is unknown.

Noted in #37

@tri-adam tri-adam merged commit 8be4f6b into master Apr 6, 2020
@tri-adam tri-adam deleted the version branch April 6, 2020 14:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants