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

ci: add goreleaser workflow for release #788

Merged
merged 1 commit into from
Feb 7, 2022
Merged

Conversation

aramase
Copy link
Member

@aramase aramase commented Feb 3, 2022

Signed-off-by: Anish Ramasekar anish.ramasekar@gmail.com

Reason for Change:

  • Use goreleaser for generating changelog when a new tag is published

Requirements

  • squashed commits
  • included documentation
  • added unit tests and e2e tests (if applicable).

Issue Fixed:

fixes #68

Does this change contain code from or inspired by another project?

  • Yes
  • No

If "Yes," did you notify that project's maintainers and provide attribution?

Special Notes for Reviewers:

Testing in my fork:

Signed-off-by: Anish Ramasekar <anish.ramasekar@gmail.com>
@codecov-commenter
Copy link

Codecov Report

Merging #788 (4c3bf1d) into master (047d148) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #788   +/-   ##
=======================================
  Coverage   61.65%   61.65%           
=======================================
  Files           7        7           
  Lines         785      785           
=======================================
  Hits          484      484           
  Misses        267      267           
  Partials       34       34           

@aramase aramase requested a review from nilekhc February 4, 2022 17:07
@aramase aramase merged commit 17b7d60 into Azure:master Feb 7, 2022
@aramase aramase deleted the goreleaser branch February 7, 2022 17:44
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.

Automate release notes
3 participants