Skip to content

Use these across the whole org #12

Closed
@penelopeysm

Description

@penelopeysm

Followup from #11

@shravanngoswamii, I've stuck with two separate workflows because I think it's clearer (especially when, say, you want to trigger the DocsNav part independently; it's a bit confusing to see the action labelled as 'Documentation' which implies that running it will rebuild the docs). Then I fixed a couple of bugs, and I also stuck a setup-julia inside DocsNav since it runs very quickly anyway. And I think we are good to go :)

I think the two workflows in here can be copy pasted into pretty much all repositories:

https://github.com/TuringLang/actions/tree/main/example_workflows

note, when using this Docs.yml we should also get rid of the call to deploydocs in docs/make.jl. That's super easy to forget.

I tested this out on DynamicPPL.jl and TuringBenchmarking.jl and they both work perfectly (and the navbar thing is fixed now).

Feel free to do as many or as few of them as you want!

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions