Skip to content

Conversation

@vitcpp
Copy link
Contributor

@vitcpp vitcpp commented Oct 16, 2025

No description provided.

push:
branches:
- "master"
workflow_dispatch:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm all for adding workflow_dispatch:, but why are you removing the push: branches: - "master" lines?

Copy link
Contributor

@esabol esabol Oct 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Never mind. I get it. We want the docs to only update when there's a new release. May I suggest the following instead?

on:
  release:
    types: [published]
  workflow_dispatch:

That will trigger automatically only when a new release is published. In the context of a GitHub Actions workflow, "published" means that a release has been finalized and made visible to the public, or specifically, marked as a non-draft and non-prerelease version. This is distinct from simply saving a draft.

Reference: https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#release

The docs should be deployed when a new release is publishing. There is
no point to deploy the docs every time when the master branch is
updated. The proposed change sets automatic doc deployment only on a
new release publication or manually.
@vitcpp
Copy link
Contributor Author

vitcpp commented Oct 17, 2025

@esabol Thank you for the idea. I've added doc deployment on release publication.

@esabol
Copy link
Contributor

esabol commented Oct 17, 2025

Looks good, I hope this will get the GitHub Actions workflow to update the documentation on the website working again.

This PR will also close issue #132.

@vitcpp vitcpp merged commit 5457452 into postgrespro:master Oct 17, 2025
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants