You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@datafusion.apache.org by ti...@apache.org on 2024/12/05 22:10:27 UTC
(datafusion-site) branch site/enable-ci-publish created (now 93da803)
This is an automated email from the ASF dual-hosted git repository.
timsaucer pushed a change to branch site/enable-ci-publish
in repository https://gitbox.apache.org/repos/asf/datafusion-site.git
at 93da803 Enable CI to publish main
This branch includes the following new commits:
new 93da803 Enable CI to publish main
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@datafusion.apache.org
For additional commands, e-mail: commits-help@datafusion.apache.org
(datafusion-site) 01/01: Enable CI to publish main
Posted by ti...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
timsaucer pushed a commit to branch site/enable-ci-publish
in repository https://gitbox.apache.org/repos/asf/datafusion-site.git
commit 93da803e4d3acec0c68dea0137041817d84c9b41
Author: Tim Saucer <ti...@maymobility.com>
AuthorDate: Thu Dec 5 17:10:09 2024 -0500
Enable CI to publish main
---
.github/workflows/publish-site.yml | 9 +++------
.github/workflows/stage-site.yml | 19 ++++++-------------
2 files changed, 9 insertions(+), 19 deletions(-)
diff --git a/.github/workflows/publish-site.yml b/.github/workflows/publish-site.yml
index a8f9752..93cf8a3 100644
--- a/.github/workflows/publish-site.yml
+++ b/.github/workflows/publish-site.yml
@@ -1,8 +1,6 @@
# This workflow runs the pelican build process after any branch has merged
# into main and pushes the result to the branch `asf-site`.
-#
-# Publishing is currently disabled until the staging branch process has been validated
-# To enable, remove the publish: false and uncomment the following lines
+
name: Publish main
on:
push:
@@ -16,6 +14,5 @@ jobs:
- uses: actions/checkout@v4
- uses: apache/infrastructure-actions/pelican@main
with:
- publish: 'false'
- # destination: 'asf-site'
- # gfm: 'false'
+ destination: 'asf-site'
+ gfm: 'false'
diff --git a/.github/workflows/stage-site.yml b/.github/workflows/stage-site.yml
index ffd264d..80ef6fc 100644
--- a/.github/workflows/stage-site.yml
+++ b/.github/workflows/stage-site.yml
@@ -1,16 +1,9 @@
-# This workflow ensures that any PR targeted at main will build properly.
-# A failure in this workflow should prevent any merging into main. This will
-# build a new branch similar to the PR head branch but with "-staging"
-# appended to the end. If only runs for head branches that match "site/".
-#
-# If you wish to stage your site changes, then you simply need to open
-# a PR with a head branch of `site/` that targets `main`.
-#
-# For example, if you open a PR to merge `site/awesome-update` then this
-# workflow will create a branch `site/awesome-update-staging` that will
-# contain the built contents of the site. A separate ASF process will
-# identify that branch and stage your preview as
-# datafusion-awesome-update.staged.apache.org
+# This workflow will create a staged version of the website. The last branch for which this workflow
+# was run will be published to https://datafusion.staged.apache.org/
+# To enable this work flow, you simply need a PR that has a branch name that begins with `site/`
+# and targets `main`. This workflow will build the site and push the results into the branch
+# `asf-staging`. From there, the ASF infrastructure will identify that a stage site has been
+# built and will publish to the link above.
name: Stage Site
on:
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@datafusion.apache.org
For additional commands, e-mail: commits-help@datafusion.apache.org