Skip to content

Commit

Permalink
Fix out of date doc build
Browse files Browse the repository at this point in the history
  • Loading branch information
bgroenks96 committed Dec 9, 2024
1 parent 6ceac6e commit d8687d6
Show file tree
Hide file tree
Showing 4 changed files with 17 additions and 12 deletions.
1 change: 1 addition & 0 deletions docs/Project.toml
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
[deps]
ArgParse = "c7e460c6-2fb9-53a9-8c5b-16f535851c63"
CryoGrid = "a535b82e-5f3d-4d97-8b0b-d6483f5bebd5"
Distributions = "31c24e10-a181-5473-b8eb-7969acd0382f"
Documenter = "e30172f5-a6a5-5a46-863b-614d45cd2de4"
Expand Down
20 changes: 16 additions & 4 deletions docs/make.jl
Original file line number Diff line number Diff line change
@@ -1,10 +1,21 @@
using ArgParse
using CryoGrid
using Documenter
using Literate

# ENV["LOCALDOCS"] = "true"
s = ArgParseSettings()
@add_arg_table! s begin
"--local", "-l"
action = :store_true
help = "Local docs build mode"
"--draft", "-d"
action = :store_true
help = "Whether to build docs in draft mode, i.e. skipping execution of examples and doctests"
end
parsed_args = parse_args(ARGS, s)

IS_LOCAL = haskey(ENV,"LOCALDOCS") && ENV["LOCALDOCS"] == "true"
IS_LOCAL = parsed_args["local"] || parse(Bool, get(ENV, "LOCALDOCS", "false"))
IS_DRAFT = parsed_args["draft"] || parse(Bool, get(ENV, "DRAFTDOCS", "false"))
if haskey(ENV, "GITHUB_ACTIONS")
ENV["JULIA_DEBUG"] = "Documenter"
end
Expand All @@ -22,7 +33,6 @@ const modules = [
CryoGrid.Soils,
CryoGrid.Snow,
CryoGrid.Surface,
CryoGrid.Presets,
CryoGrid.Diagnostics,
# solvers
CryoGrid.DiffEq,
Expand Down Expand Up @@ -65,6 +75,7 @@ example_docpages = map(example_docfiles) do f
end

makedocs(
repo=Remotes.GitHub("CryoGrid", "CryoGrid.jl"),
modules=modules,
sitename="CryoGrid.jl",
authors="Brian Groenke, Moritz Langer, Jan Nitzbon",
Expand All @@ -73,6 +84,8 @@ makedocs(
canonical = "https://cryogrid.github.io/CryoGrid.jl/v0",
),
warnonly=true, # don't fail when there are errors
doctest=!IS_DRAFT,
draft=IS_DRAFT,
pages=["Home" => "index.md",
"Installation" => "installation.md",
"Getting Started" => "quickstart.md",
Expand Down Expand Up @@ -107,7 +120,6 @@ makedocs(
"CryoGridLite" => "api/solvers/lite_implicit.md",
],
"Diagnostics" => "api/diagnostics.md",
"Presets" => "api/presets.md",
],
])

Expand Down
7 changes: 0 additions & 7 deletions docs/src/api/presets.md

This file was deleted.

1 change: 0 additions & 1 deletion docs/src/manual/architecture.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,6 @@ The `CryoGrid` module provided by CryoGrid.jl is organized into a series of subm
|`Tiles`|Defines the `Tile` and `Stratigraphy` types for constructing 1D land models.|`Utils`,`Numerics`,`InputOutput`|
|`DiffEq`|Provides dispatches and utilities for integrating with solvers from the SciML `OrdinaryDiffEq` package.|`Utils`,`Numerics`,`InputOutput`|
|`LiteImplicit`|Provides an implementation of the `CryoGridLite` solver scheme from Langer et al. 2023.|`Utils`,`Numerics`|
|`Presets`|Provides pre-defined stratigraphies, forcings, and layer configurations to facilitate rapid prototyping.|`Utils`,`Numerics`,`InputOutput`,`Heat`,`Hydrology`,`Soils`|

Note that all submodules depend on the top-level `CryoGrid` module which declares all of the "core" types and [method interfaces](https://docs.julialang.org/en/v1/manual/interfaces/) for defining model behavior. Each submodule may additionally define its own method interfaces related to its own specific process(es) or layer(s).

Expand Down

2 comments on commit d8687d6

@bgroenks96
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JuliaRegistrator
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Registration pull request created: JuliaRegistries/General/121042

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.23.0 -m "<description of version>" d8687d653fe521451642a006987cff7c021fda3d
git push origin v0.23.0

Please sign in to comment.