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

Only deploy website on release #424

Merged
merged 1 commit into from
Dec 8, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 6 additions & 16 deletions .github/workflows/web.yml
Original file line number Diff line number Diff line change
Expand Up @@ -17,22 +17,12 @@ on:
# completely broke oranda/mdbook. Sadly we don't provide previews (yet)!
pull_request:

# Whenever a workflow called "Release" completes, update the docs!
#
# If you're using cargo-dist, this is recommended, as it will ensure that
# oranda always sees the latest release right when it's available. Note
# however that Github's UI is wonky when you use workflow_run, and won't
# show this workflow as part of any commit. You have to go to the "actions"
# tab for your repo to see this one running (the gh-pages deploy will also
# only show up there).
workflow_run:
workflows: ["Release"]
types:
- completed
# Every PR runs the first step of the Release workflow. Without this branch
# filter, that workflow run would trigger the website release on every merge.
# Instead, we only want to trigger when a release is actually cut.
branches: [master]
# Deploy website when release is published. This is a manual edit. Eventually
# hopefully we can configure oranda to do generate it like this
# https://github.com/axodotdev/oranda/issues/646
release:
# This only triggers for stable releases
types: [released]

# Run manually
workflow_dispatch:
Expand Down
Loading