Re: [PR] docs: deploy docs when merging to master [superset]
mistercrunch merged PR #27956: URL: https://github.com/apache/superset/pull/27956 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
Re: [PR] docs: deploy docs when merging to master [superset]
mistercrunch commented on PR #27956: URL: https://github.com/apache/superset/pull/27956#issuecomment-2046284774 @rusackas I'll let you merge this one since you wanted to use it for troubleshooting the `.htaccess` stuffs -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
[PR] docs: deploy docs when merging to master [superset]
mistercrunch opened a new pull request, #27956: URL: https://github.com/apache/superset/pull/27956 ### SUMMARY 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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
