Skip to content

termnames

termnames #337

Triggered via pull request September 3, 2023 20:32
@paldaypalday
synchronize #299
pa/termnames
Status Success
Total duration 5m 2s
Artifacts

docs.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

7 warnings
Documentation: ../../../.julia/packages/Documenter/bYYzK/src/Utilities/Utilities.jl#L34
13 docstrings not included in the manual: StatsModels.termnames :: Tuple{StatisticalModel} StatsModels.termnames :: Union{Tuple{InterceptTerm{H}}, Tuple{H}} where H StatsModels.termnames :: Tuple{FormulaTerm} StatsModels.fuzzymatch :: Tuple{Any, Symbol} StatsModels.checknamesexist :: Tuple{FormulaTerm, Any} StatsModels.isnested StatsModels.has_schema :: Tuple{AbstractTerm} StatsModels.termvars :: Tuple{AbstractTerm} StatsModels.checkcol :: Tuple{Any, Symbol} Base.convert :: Tuple{Type{StatsModels.ContrastsMatrix{StatsModels.FullDummyCoding}}, StatsModels.ContrastsMatrix} StatsModels.termsyms :: Tuple{AbstractTerm} StatsModels.reshape_last_to_i :: Tuple{Any, Any} StatsModels.needs_intercept :: Tuple{AbstractMatrix} These are docstrings in the checked modules (configured with the modules keyword) that are not included in @docs or @autodocs blocks.
Documentation: ../../../.julia/packages/Documenter/bYYzK/src/Documenter.jl#L800
removing `stable` and linking `stable` to `v0.7.2`.
Documentation: ../../../.julia/packages/Documenter/bYYzK/src/Documenter.jl#L800
removing `v0.7` and linking `v0.7` to `v0.7.2`.
Documentation: ../../../.julia/packages/Documenter/bYYzK/src/Documenter.jl#L800
removing `v0.6` and linking `v0.6` to `v0.6.33`.
Documentation: ../../../.julia/packages/Documenter/bYYzK/src/Documenter.jl#L800
removing `v0.2` and linking `v0.2` to `v0.2.6`.
Documentation: ../../../.julia/packages/Documenter/bYYzK/src/Documenter.jl#L800
removing `v0.6.8` and linking `v0.6.8` to `0.6.8`.
Documentation
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/