tree 41d6afd81757560999b130b117acf2fd97470a1c
parent 894c802a42cb62a1367ff42b0898609d9dfd1f04
author Shannon Deminick <sdeminick@gmail.com> 1622480778 +1000
committer GitHub <noreply@github.com> 1622480778 +1000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJgtReKCRBK7hj4Ov3rIwAAB/YIACi20Yy8H7c11CA8p8q/CW9/
 M+zohbUiTdu0G/k4dOf1nfYpcNsFRBpV3E3eJPC1Q0qa138GhC0u7WgSE8LktTHi
 O6J8BZpmlXc/o5rwOqWvhgXbkcLD6tbx4Yd8tJddHZ6Tv8O8JqYDvQlDZ+kyY881
 0/x8ZGHctoOpP2PO32Hhfr4EbZnL/3PDMW6ruE00Z8XSEfyA2DCjHMUROPGaVH2m
 vypNd6brhagLRqCRRJU3NQGymXApgkd8dc4ZZvjsUIEUGf7CHa9zP8pF7LnuyCjF
 A4avAIUmBFZEpffrXRYd/SqkEcsfRmnGTbPkNEGyX3mDFeMr1mki3+4FnNRoeLU=
 =lONA
 -----END PGP SIGNATURE-----
 

Updating .asf.yaml to be compliant with apache infra

This adds the changes to support the apache infra change request. This also then provides the ability to have a staging site if/when we want to do that. The docs for staging are here https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebSiteDeploymentServiceforGitRepositories 

For the time being though, I think this change satisfies the apache infra requirements.

Part of the requirements is:

> It is important to note that the .asf.yaml file MUST be present at the
root of the file system in the branch you wish to publish. The 'whoami'
parameter acts as a guard, ensure that only the intended branch is used
for publishing.

which I think means that this file must be in the root of the asf-site branch (and any other branch that hosts the site, like staging eventually). Probably should commit to master and merge up to asf-site. Though it would be nice to make asf-site the default branch since we only really ever use that but I'm unsure how to do that.

Let me know what you think.