This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/fluo-website.git
The following commit(s) were added to refs/heads/asf-staging by this push:
new 51fa6c7 Automatic Site Publish by Buildbot
51fa6c7 is described below
commit 51fa6c7b23e921a8a12388452d22dd92758a4206
Author: buildbot <[email protected]>
AuthorDate: Thu Sep 10 14:38:30 2020 +0000
Automatic Site Publish by Buildbot
---
output/README.md | 6 +++++-
output/feed.xml | 4 ++--
2 files changed, 7 insertions(+), 3 deletions(-)
diff --git a/output/README.md b/output/README.md
index d106058..7af75cd 100644
--- a/output/README.md
+++ b/output/README.md
@@ -81,7 +81,11 @@ git remote update upstream
git push upstream upstream/asf-staging:asf-site
```
-Note that Step 3 should always be a fast-forward merge. That is, there should
+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
diff --git a/output/feed.xml b/output/feed.xml
index 1a093b9..d654bf6 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>Fri, 14 Aug 2020 11:56:11 +0000</pubDate>
- <lastBuildDate>Fri, 14 Aug 2020 11:56:11 +0000</lastBuildDate>
+ <pubDate>Thu, 10 Sep 2020 14:38:24 +0000</pubDate>
+ <lastBuildDate>Thu, 10 Sep 2020 14:38:24 +0000</lastBuildDate>
<generator>Jekyll v3.9.0</generator>
