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

[semver:patch] Update bash curling best practices and bump to 1.1.6 #81

Merged
merged 3 commits into from
May 5, 2021

Conversation

thomasrockhu
Copy link
Contributor

@thomasrockhu thomasrockhu commented May 3, 2021

Update the bash script download with best practices

@codecov
Copy link

codecov bot commented May 3, 2021

Codecov Report

Merging #81 (c1ee288) into master (ab0646f) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #81   +/-   ##
=======================================
  Coverage   88.88%   88.88%           
=======================================
  Files           3        3           
  Lines          18       18           
=======================================
  Hits           16       16           
  Misses          2        2           
Flag Coverage Δ
backend ?
frontend ?

Flags with carried forward coverage won't be shown. Click here to find out more.


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 76e9fbe...c1ee288. Read the comment docs.

@thomasrockhu thomasrockhu changed the title Update bash curling best practices and bump to 1.1.6 [semver:patch] Update bash curling best practices and bump to 1.1.6 May 4, 2021
@thomasrockhu thomasrockhu merged commit b95c45f into master May 5, 2021
@thomasrockhu thomasrockhu deleted the 1.1.6 branch May 5, 2021 20:25
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.

2 participants