Skip to content

Commit

Permalink
fix docs/make.jl
Browse files Browse the repository at this point in the history
  • Loading branch information
j-fu committed Nov 13, 2023
1 parent fc0fa6d commit 78b2a9a
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions docs/make.jl
Original file line number Diff line number Diff line change
Expand Up @@ -11,12 +11,11 @@ function rendernotebook(name)
end

function make_all()
thisdir = pwd()
Pkg.activate(joinpath(@__DIR__, "..", "examples"))
Pkg.develop(; path = joinpath(thisdir, ".."))
Pkg.develop(; path = joinpath(@__DIR__, ".."))
Pkg.instantiate()
Pkg.activate(thisdir)
rendernotebook("pluto-examples")
Pkg.activate(@__DIR__)

makedocs(; sitename = "Triangulate.jl",
modules = [Triangulate],
Expand Down

2 comments on commit 78b2a9a

@j-fu
Copy link
Member Author

@j-fu j-fu commented on 78b2a9a Nov 13, 2023

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/95267

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 v2.3.1 -m "<description of version>" 78b2a9a763b8a365b085f7ac39e6afa90de2b495
git push origin v2.3.1

Please sign in to comment.