pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  

help / color / mirror / Atom feed

[pgjdbc/pgjdbc] PR #3819: create action to deploy docs to https://pgjdbc.github.io/
6+ messages / 3 participants
[nested] [flat]

* [pgjdbc/pgjdbc] PR #3819: create action to deploy docs to https://pgjdbc.github.io/
@ 2025-09-26 15:24  "davecramer (@davecramer)" <[email protected]>
  0 siblings, 0 replies; 6+ messages in thread

From: davecramer (@davecramer) @ 2025-09-26 15:24 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3819: create action to deploy docs to https://pgjdbc.github.io/
@ 2025-09-26 15:37  "vlsi (@vlsi)" <[email protected]>
  4 siblings, 0 replies; 6+ messages in thread

From: vlsi (@vlsi) @ 2025-09-26 15:37 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on .github/workflows/docs.yml)

We probably want running it with the latest tag only. For instance, if we release a fix for an older version, we don't updating the site from the old sources.

One of the options could be going for a manual execution (see https://github.com/pgjdbc/pgjdbc/blob/c1c469e8fd9d37f0bcd71966753d72fb584c1f3f/.github/workflows/rel...)

Another option could be skipping the workflow for "non-mainline" tags somehow.

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3819: create action to deploy docs to https://pgjdbc.github.io/
@ 2025-09-26 15:48  "davecramer (@davecramer)" <[email protected]>
  4 siblings, 0 replies; 6+ messages in thread

From: davecramer (@davecramer) @ 2025-09-26 15:48 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(on .github/workflows/docs.yml)

good point.

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3819: create action to deploy docs to https://pgjdbc.github.io/
@ 2025-09-26 18:40  "sehrope (@sehrope)" <[email protected]>
  4 siblings, 0 replies; 6+ messages in thread

From: sehrope (@sehrope) @ 2025-09-26 18:40 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

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

Do we publish releases for back patched versions? If so, I think this would trigger a build when that happens and the source checked out would default to the ref that generated the release event.

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3819: create action to deploy docs to https://pgjdbc.github.io/
@ 2025-09-26 19:01  "davecramer (@davecramer)" <[email protected]>
  4 siblings, 0 replies; 6+ messages in thread

From: davecramer (@davecramer) @ 2025-09-26 19:01 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

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

I guess we can just leave it as manual ?

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: [pgjdbc/pgjdbc] PR #3819: create action to deploy docs to https://pgjdbc.github.io/
@ 2025-09-29 19:05  "vlsi (@vlsi)" <[email protected]>
  4 siblings, 0 replies; 6+ messages in thread

From: vlsi (@vlsi) @ 2025-09-29 19:05 UTC (permalink / raw)
  To: pgjdbc/pgjdbc <[email protected]>

(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.

^ permalink  raw  reply  [nested|flat] 6+ messages in thread

end of thread, other threads:[~2025-09-29 19:05 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-09-26 15:24 [pgjdbc/pgjdbc] PR #3819: create action to deploy docs to https://pgjdbc.github.io/ "davecramer (@davecramer)" <[email protected]>
2025-09-26 15:37 ` "vlsi (@vlsi)" <[email protected]>
2025-09-26 15:48 ` "davecramer (@davecramer)" <[email protected]>
2025-09-26 18:40 ` "sehrope (@sehrope)" <[email protected]>
2025-09-26 19:01 ` "davecramer (@davecramer)" <[email protected]>
2025-09-29 19:05 ` "vlsi (@vlsi)" <[email protected]>

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox