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

Show branch and commit instead of tag when not on release branch #651

Merged
merged 1 commit into from
Feb 19, 2021

Conversation

shahankhatch
Copy link
Contributor

Closes: #627

Description


For contributor use:

  • Targeted PR against correct branch (see CONTRIBUTING.md)
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Code follows the module structure standards.
  • Wrote unit and integration tests
  • Updated relevant documentation (docs/) or specification (x/<module>/spec/)
  • Added relevant godoc comments.
  • Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • Re-reviewed Files changed in the Github PR explorer

For admin use:

  • Added appropriate labels to PR (ex. WIP, R4R, docs, etc)
  • Reviewers assigned
  • Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)

Makefile Show resolved Hide resolved
@shahankhatch shahankhatch merged commit 651f646 into main Feb 19, 2021
@shahankhatch shahankhatch deleted the shahan/main_reports_v3 branch February 19, 2021 14:30
@alessio alessio mentioned this pull request Mar 4, 2021
11 tasks
alessio pushed a commit that referenced this pull request Mar 4, 2021
Most users run builds on tags and not on release
branches. Because of a regression introduced in
651f646, the buildsystem is now assuming that
the opposite is true, therefore it is longer capable
to handle version strings correctly.

Don't use git describe --tags to avoid relying on
non-annotated tags.

BRANCH name detection is ephemeral and unreliable,
and should always be used only as last resort.

Ref: #651
alessio pushed a commit that referenced this pull request Mar 4, 2021
Most users run builds on tags and not on release
branches. Because of a regression introduced in
651f646, the buildsystem is now assuming that
the opposite is true, therefore it is longer capable
to handle version strings correctly.

Don't use git describe --tags to avoid relying on
non-annotated tags.

BRANCH name detection is ephemeral and unreliable,
and should always be used only as last resort.

Ref: #651
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.

Building main branch reports v3.0.0 in gaiad version
3 participants