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 note about nomsgpack tag to the readme #2703

Merged
merged 2 commits into from May 1, 2021

Conversation

y-yagi
Copy link
Contributor

@y-yagi y-yagi commented Apr 24, 2021

I think this information is useful for users that don't use MsgPack rendering.

I think this information is useful for users that don't use `MsgPack` rendering.
@appleboy appleboy changed the title [ci skip] Add note about nomsgpack tag to the readme Add note about nomsgpack tag to the readme Apr 26, 2021
@appleboy appleboy added this to the v1.8 milestone Apr 28, 2021
@codecov
Copy link

codecov bot commented May 1, 2021

Codecov Report

Merging #2703 (c576a68) into master (1acb459) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #2703   +/-   ##
=======================================
  Coverage   98.67%   98.67%           
=======================================
  Files          41       41           
  Lines        2036     2036           
=======================================
  Hits         2009     2009           
  Misses         15       15           
  Partials       12       12           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1acb459...c576a68. Read the comment docs.

@appleboy appleboy merged commit 5452a1d into gin-gonic:master May 1, 2021
@y-yagi y-yagi deleted the add-note-about-nomsgpack branch May 1, 2021 06:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants