From f1fbe844d2b41a503f291078e430a6fbf9f89847 Mon Sep 17 00:00:00 2001 From: Jack Baldry Date: Wed, 8 Jan 2025 08:38:03 +0000 Subject: [PATCH] Use tags only workflow behavior Without this, the action assumes there is a release branch that a tag is made on because that is common to most other Grafana repositories. Those repositories maintain a long-lived release branch to facilitate backports to documentation and code. Since grafana/oncall doesn't follow this pattern, it doesn't make sense to try and discover the matching release branch. That action behavior is disabled by the `tags_only: true` setting. Signed-off-by: Jack Baldry --- .github/workflows/publish-technical-documentation-release.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.github/workflows/publish-technical-documentation-release.yml b/.github/workflows/publish-technical-documentation-release.yml index e91b642a5..d2626d723 100644 --- a/.github/workflows/publish-technical-documentation-release.yml +++ b/.github/workflows/publish-technical-documentation-release.yml @@ -25,4 +25,6 @@ jobs: release_tag_regexp: "^v(0|[1-9][0-9]*)\\.(0|[1-9][0-9]*)\\.(0|[1-9][0-9]*)$" release_branch_regexp: "^release-(0|[1-9][0-9]*)\\.(0|[1-9][0-9]*)$" release_branch_with_patch_regexp: "^release-(0|[1-9][0-9]*)\\.(0|[1-9][0-9]*)\\.(0|[1-9][0-9]*)$" + # This repository only releases from the tag reference and not from long-lived release branches. + tags_only: true website_directory: content/docs/oncall