Closed dave2wave closed 5 months ago
AFAICT the code currently does the same as the BuildBot job. That certainly works for staging builds, as can be seen in www-site preview branches. But I agree it looks odd to see the full .asf.yaml in the staging branch.
I think maybe the code needs to copy just the staging and publish stanzas.
Also, some projects may use a different branch for the published site, so that needs to be obtained from the existing .asf.yaml
the staging part of the .asf.yaml is branch specific aiui, so only the bits matching the whoami
will be evaluated.
The staging stanza is only branch specific if it contains a whoami clause. [1]
Also the autostage clause is not affected by the whoami clause.
Thank you
I see the following in the action at https://github.com/apache/infrastructure-actions/blob/main/pelican/action.yml#L102-L104
This copies the
.asf.yaml
file.. This is not really what is needed:For preview we need:
and for branch
ash-site
: