rzo1 commented on PR #9:
URL: https://github.com/apache/openjpa-site/pull/9#issuecomment-6734836068
@solomax the `staging:` block only takes effect on the branch being served:
ASF reads `.asf.yaml` from the pushed branch and runs only blocks whose
`whoami` matches that branch. On main it's ignored, and there's no
`asf-staging` branch yet; our workflow only targets `asf-site` (and deploy is
skipped on PRs).
I'd do it like storm-site / stormcrawler-site:
1. Create `asf-staging` from `asf-site` with this in its `.asf.yaml`:
```yaml
staging:
profile: ~
whoami: asf-staging
```
2. Add a `publish-staging.yml` (workflow_dispatch) that runs the same build,
then `rsync -a --delete output/ asf-staging/output/`, commits and pushes. No
`persist-credentials: false` on those checkouts.
The deploy job needs the same treatment: it still has `npm ci` with the npm
cache (no lock file), and `infrastructure-actions/pelican` rebuilds without `-s
pelican.auto.py`, dropping our theme and assets. I'd replace it with the same
rsync-and-push into `asf-site`, and drop the `pelican:` block on main.
I can create the `asf-staging` branch if that works for you.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
