Skip to content

Commit

Permalink
github: don't trigger docs update on non-release tags
Browse files Browse the repository at this point in the history
When triggered from a tag, our gh-pages update script considers this as
a new release. This means potentially (if it's the first tag in the vX.Y
series) creating a new vX.Y/ subdir in the docs, linking that as the
latest stable release etc. We definitely don't want this to happen for
devel or rc or such tags. Modifying the workflow file to only act on
well-formed release tags (like v1.2.3) is the most straightforward way
to fix this.
  • Loading branch information
marquiz committed Mar 28, 2024
1 parent 3691621 commit b4bfeaf
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion .github/workflows/publish-docs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ on:
- main
- release-*
tags:
- v*
- v[0-9]+.[0-9]+.[0-9]+

env:
GO_VERSION: "1.22.1"
Expand Down

0 comments on commit b4bfeaf

Please sign in to comment.