tisonkun opened a new pull request, #109: URL: https://github.com/apache/steve/pull/109
Configure ASF staging for generated `site/<name>-staging` branches, served at `https://steve-<name>.staged.apache.org`. The `whoami: asf-staging` guard keeps source branches from being staged; the existing production Pelican configuration is unchanged. This prepares the website rewrite for review before production deployment. The follow-up website PR will add the build workflow and include `.asf.yaml` in its generated output before pushing that output to a staging branch. This configuration alone does not build a site or automatically preview pull requests. ASF [staging configuration](https://github.com/apache/infrastructure-asfyaml#autostage) is branch-specific. Merging this first lets subsequent source branches inherit it; generated output branches must also contain the configuration. Validation: - Full ASF schema validation with `infrastructure-asfyaml` at `c10410aed8ea066e48826fc4bae0f9cf1dfe9025`. - Dry-run staging routing: `site/website-staging` maps to `https://steve-website.staged.apache.org`; `asf-staging` maps to the default staging domain; `trunk`, `codex/site-preview`, `site/website`, and `asf-site` do not stage. - `uv run ruff format .`, `uv run ruff check --fix .`, and `uv run mypy --ignore-missing-imports .` passed in `v3/`. - `git diff --check` passed. -- 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]
