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

For a 0.6.1 release #113

Merged
merged 14 commits into from
Feb 22, 2022
Merged

For a 0.6.1 release #113

merged 14 commits into from
Feb 22, 2022

Conversation

ablaom
Copy link
Member

@ablaom ablaom commented Feb 21, 2022

@codecov-commenter
Copy link

codecov-commenter commented Feb 21, 2022

Codecov Report

Merging #113 (0e19298) into master (abf145f) will increase coverage by 1.25%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #113      +/-   ##
==========================================
+ Coverage   94.79%   96.05%   +1.25%     
==========================================
  Files          20       21       +1     
  Lines         846      861      +15     
==========================================
+ Hits          802      827      +25     
+ Misses         44       34      -10     
Impacted Files Coverage Δ
src/fit/iwls.jl 100.00% <ø> (ø)
src/glr/constructors.jl 100.00% <ø> (ø)
src/mlj/classifiers.jl 100.00% <ø> (+50.00%) ⬆️
src/mlj/regressors.jl 56.25% <ø> (+49.58%) ⬆️
src/fit/analytical.jl 100.00% <100.00%> (ø)
src/fit/proxgrad.jl 95.12% <100.00%> (ø)
src/glr/d_l2loss.jl 100.00% <100.00%> (ø)
src/glr/d_logistic.jl 100.00% <100.00%> (ø)
src/glr/d_robust.jl 100.00% <100.00%> (ø)
src/glr/prox.jl 100.00% <100.00%> (ø)
... and 11 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 abf145f...0e19298. Read the comment docs.

@ablaom ablaom merged commit f4a38dd into master Feb 22, 2022
@ablaom
Copy link
Member Author

ablaom commented Feb 22, 2022

@tlienart If you don't object, I suggest including the branch when triggering releases, as in @JuliaRegegistrator register branch=master. I think the default behaviour is to use the GH default branch, which is dev in this case. I have been using master as the release branch (and for nothing else).

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.

5 participants