Message-ID: <gh-pgjdbc-pgjdbc-3819-rc2388963073@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 29 Sep 2025 19:05:34 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3819: create action to deploy docs to https://pgjdbc.github.io/
In-Reply-To: <gh-pgjdbc-pgjdbc-3819-rc2383197378@github.com>
References: <gh-pgjdbc-pgjdbc-3819@github.com> <gh-pgjdbc-pgjdbc-3819-rc2383197378@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 2388963073
X-GitHub-Comment-Type: review_comment
X-GitHub-Commit: ac7b961e2987f6153d9279fbacde65ec9d47a7e6
X-GitHub-Issue: 3819
X-GitHub-Line: 5
X-GitHub-Path: .github/workflows/docs.yml
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: review_comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3819#discussion_r2388963073
Content-Type: text/plain; charset=utf-8

(on .github/workflows/docs.yml:5)

I believe "release published" is not the right trigger.
Releasing the fix for an older release would update the site with an old contents. It is not something we want.

We should rather add a branch like `website` which we could update during the release if releasing from the master branch.