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

Handle tag-match-latest on Git tag event #8

Merged
merged 2 commits into from
Oct 31, 2020
Merged

Conversation

crazy-max
Copy link
Member

Closes #7

@codecov
Copy link

codecov bot commented Oct 31, 2020

Codecov Report

Merging #8 into master will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master       #8   +/-   ##
=======================================
  Coverage   71.21%   71.21%           
=======================================
  Files           3        3           
  Lines          66       66           
  Branches       14       14           
=======================================
  Hits           47       47           
  Misses          6        6           
  Partials       13       13           
Impacted Files Coverage Δ
src/meta.ts 72.72% <100.00%> (ø)

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 b4c9b21...84f6a41. Read the comment docs.

@Zageron
Copy link

Zageron commented Oct 31, 2020

Resolves #7, tested. Thank you! :D

@crazy-max crazy-max merged commit 52c4b1a into master Oct 31, 2020
@crazy-max crazy-max deleted the tag-match-latest branch October 31, 2020 18:52
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.

Unless you have tag-match set, tag-match-latest does nothing on tag push.
2 participants