(superset) 01/01: docs: deploy docs when merging to master

[ma...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

maximebeauchemin pushed a commit to branch docs_only_master
in repository https://gitbox.apache.org/repos/asf/superset.git

commit ecd38152188d35adb25780d6b8d42887fa74363c
Author: Maxime Beauchemin <ma...@gmail.com>
AuthorDate: Tue Apr 9 14:38:19 2024 -0700

    docs: deploy docs when merging to master
    
    I believe the intention is to have the docs
    aligned with what is on `master`, currently pushing on a release
    branch will trigger a potential regression.
    
    It could be reasonable for the docs to be aligned with the latest
    release, but if that was the intention we should deploy the
    docs as part of the release process, and avoid previous release branch
    from deploying the docs.
    
    I think this happened by mistake on
    https://github.com/apache/superset/pull/27390/files#diff-1f3b6eaac4370772e5f0d6cebab7906e0a83ce78e07f6ae8a239c06b33a420d4R9
    when the intention was to trigger CI on release branches, not to deploy
    the docs.
---
 .github/workflows/superset-docs-deploy.yml | 1 -
 1 file changed, 1 deletion(-)

diff --git a/.github/workflows/superset-docs-deploy.yml b/.github/workflows/superset-docs-deploy.yml
index 07bba70edd..a6eefe3644 100644
--- a/.github/workflows/superset-docs-deploy.yml
+++ b/.github/workflows/superset-docs-deploy.yml
@@ -6,7 +6,6 @@ on:
       - "docs/**"
     branches:
       - "master"
-      - "[0-9].[0-9]"
 
 jobs:
   config: