dysonance / Temporal.jl

Time series implementation for the Julia language focused on efficiency and flexibility
Other
100 stars 25 forks source link

Issue 14 #18

Closed dysonance closed 6 years ago

dysonance commented 6 years ago

Addresses https://github.com/dysonance/Temporal.jl/issues/14.

Will merge master and update readme once confirmed that documentation is building and hosting properly and is sufficiently filled out.

codecov[bot] commented 6 years ago

Codecov Report

Merging #18 into master will not change coverage. The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #18   +/-   ##
=======================================
  Coverage   65.43%   65.43%           
=======================================
  Files          14       14           
  Lines         972      972           
=======================================
  Hits          636      636           
  Misses        336      336

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 95bbb42...c815596. Read the comment docs.

coveralls commented 6 years ago

Coverage Status

Coverage remained the same at 65.432% when pulling c815596af17a49575af5272a589c7432ffa000dc on issue_14 into 95bbb42b1e946b1810c045643e3f6206bcb2e434 on master.

femtotrader commented 6 years ago

I don't see link to your doc build in README.md

Do you build doc using Travis and host it as Github pages as mentioned in https://juliadocs.github.io/Documenter.jl/latest/man/hosting/

femtotrader commented 6 years ago

Content of README.md (except badges should be moved to docs directory)

dysonance commented 6 years ago

@femtotrader Yeah I'm still figuring out how the whole ecosystem works together, just started giving all this a try last night. I did read the docs on hosting GitHub pages, and thought that if I merged the branch the documentation work into master that it would handle some of that work.

I will come back to this again as soon as I get a second and go through how to set this up more carefully. Obviously I still have a long way to go yet before I get over this learning curve, but bear with me, I'll figure it out eventually :)