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

Use release tag name instead of name in log messages #109

Merged
merged 1 commit into from
Dec 24, 2020

Conversation

moorereason
Copy link
Contributor

Use the release TagName instead of Name when reporting found releases.
An example of the problem using Name:

$ go run . --repo=github.com/magefile/mage --show-details --checks=Signed-Releases
Starting [Signed-Releases]
Finished [Signed-Releases]

RESULTS
-------
Signed-Releases: Fail 10
    release found: Colors, working directory, some better errors
    !! release Colors, working directory, some better errors has no signed artifacts
    release found: Modules and go1.13 Fixes
    !! release Modules and go1.13 Fixes has no signed artifacts
    release found: v1.8.0 - Papercuts and Bug Fixes
    !! release v1.8.0 - Papercuts and Bug Fixes has no signed artifacts
    release found: v1.7.1
    !! release v1.7.1 has no signed artifacts
    release found: v1.7.0 Mage Imports
    !! release v1.7.0 Mage Imports has no signed artifacts
    release found: v1.6.2 Bug Fixes
    !! release v1.6.2 Bug Fixes has no signed artifacts
    found signed artifacts for 0 out of 6 releases

With this commit:

Signed-Releases: Fail 10
    release found: v1.10.0
    !! release v1.10.0 has no signed artifacts
    release found: v1.9.0
    !! release v1.9.0 has no signed artifacts
    release found: v1.8.0
    !! release v1.8.0 has no signed artifacts
    release found: v1.7.1
    !! release v1.7.1 has no signed artifacts
    release found: v1.7.0
    !! release v1.7.0 has no signed artifacts
    release found: v1.6.2
    !! release v1.6.2 has no signed artifacts
    found signed artifacts for 0 out of 6 releases

Use the release TagName instead of Name when reporting found releases.
An example of the problem using Name:

$ go run . --repo=github.com/magefile/mage --show-details --checks=Signed-Releases
Starting [Signed-Releases]
Finished [Signed-Releases]

RESULTS
-------
Signed-Releases: Fail 10
    release found: Colors, working directory, some better errors
    !! release Colors, working directory, some better errors has no signed artifacts
    release found: Modules and go1.13 Fixes
    !! release Modules and go1.13 Fixes has no signed artifacts
    release found: v1.8.0 - Papercuts and Bug Fixes
    !! release v1.8.0 - Papercuts and Bug Fixes has no signed artifacts
    release found: v1.7.1
    !! release v1.7.1 has no signed artifacts
    release found: v1.7.0 Mage Imports
    !! release v1.7.0 Mage Imports has no signed artifacts
    release found: v1.6.2 Bug Fixes
    !! release v1.6.2 Bug Fixes has no signed artifacts
    found signed artifacts for 0 out of 6 releases

With this commit:

Signed-Releases: Fail 10
    release found: v1.10.0
    !! release v1.10.0 has no signed artifacts
    release found: v1.9.0
    !! release v1.9.0 has no signed artifacts
    release found: v1.8.0
    !! release v1.8.0 has no signed artifacts
    release found: v1.7.1
    !! release v1.7.1 has no signed artifacts
    release found: v1.7.0
    !! release v1.7.0 has no signed artifacts
    release found: v1.6.2
    !! release v1.6.2 has no signed artifacts
    found signed artifacts for 0 out of 6 releases
@inferno-chromium inferno-chromium merged commit 329a4cf into ossf:main Dec 24, 2020
@moorereason moorereason deleted the release-tagname branch December 24, 2020 17:57
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