This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/fluo-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 103aacc Automatic Site Publish by Buildbot
103aacc is described below
commit 103aacc4d624990d08f8a783894a38620d24f1d8
Author: buildbot <[email protected]>
AuthorDate: Wed Aug 21 22:44:47 2024 +0000
Automatic Site Publish by Buildbot
---
output/README.md | 48 ++----------------------------------------------
output/feed.xml | 4 ++--
2 files changed, 4 insertions(+), 48 deletions(-)
diff --git a/output/README.md b/output/README.md
index 75c2552..aa4e1e7 100644
--- a/output/README.md
+++ b/output/README.md
@@ -68,56 +68,12 @@ replace any reference to `fluo` with `recipes`.
## Publishing
-### Automatic Staging
-
Changes pushed to our `main` branch will automatically trigger [Jekyll] to
-build our site from that branch and push the result to our `asf-staging`
-branch, where they will be served on [our default staging site][staging].
-
-### Publishing Staging to Production
-
-First, add our repository as a remote in your local clone, if you haven't
-already done so (these commands assume the name of that remote is 'upstream').
-
-Example:
-
-```bash
-git clone https://github.com/<yourusername>/fluo-website
-cd fluo-website
-git remote add upstream https://github.com/apache/fluo-website
-```
-
-Next, publish the staging site to production by updating the `asf-site` branch
-to match the contents in the `asf-staging` branch:
-
-```bash
-# Step 0: stay in main branch; you never need to switch
-git checkout main
-
-# Step 1: update your upstream remote
-git remote update upstream
-
-# Step 2: push upstream/asf-staging to upstream/asf-site
-# run next command with --dry-run first to see what it will do without making
changes
-git push upstream upstream/asf-staging:asf-site
-```
-
-A convenience script can be found that performs these steps for you, after
-asking which remote you want to use. It is located in the `main` branch at
-`_scripts/publish.sh`
-
-Note that Step 2 should always be a fast-forward merge. That is, there should
-never be any reason to force-push it if everything is done correctly. If extra
-commits are ever added to `asf-site` that are not present in `asf-staging`,
-then those branches will need to be sync'd back up in order to continue
-avoiding force pushes.
-
-The final site can be viewed [here][production].
-
+build our site from that branch and push the result to our `asf-site`
+branch, where they will be served on [our production site][production].
[Jekyll]: https://jekyllrb.com/
[production]: https://fluo.apache.org
-[staging]: https://fluo.staged.apache.org
[ti]: https://github.com/apache/fluo-website/workflows/CI/badge.svg
[tl]: https://github.com/apache/fluo-website/actions
[li]: http://img.shields.io/badge/license-ASL-blue.svg
diff --git a/output/feed.xml b/output/feed.xml
index de40037..8a73b77 100644
--- a/output/feed.xml
+++ b/output/feed.xml
@@ -5,8 +5,8 @@
<description>Apache Fluo Website</description>
<link>https://fluo.apache.org//</link>
<atom:link href="https://fluo.apache.org//feed.xml"; rel="self"
type="application/rss+xml" />
- <pubDate>Wed, 05 Jun 2024 20:41:33 +0000</pubDate>
- <lastBuildDate>Wed, 05 Jun 2024 20:41:33 +0000</lastBuildDate>
+ <pubDate>Wed, 21 Aug 2024 22:44:45 +0000</pubDate>
+ <lastBuildDate>Wed, 21 Aug 2024 22:44:45 +0000</lastBuildDate>
<generator>Jekyll v4.3.3</generator>
