errose28 commented on PR #6916: URL: https://github.com/apache/ozone/pull/6916#issuecomment-2356773937
I was talking with @sarvekshayr, who was testing this out on her forks of ozone and ozone-site and getting permission errors when ozone tried to raise a PR to ozone-site, since it would need to create a new branch for the PR in ozone-site. After some research, we will need a [personal access token](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens) (PAT) for apache/ozone to have permissions to create branches needed for PRs to apache/ozone-site. This needs ASF infra to approve, but it looks like there's already precedent for other projects doing it so we should be able to get approval. See [INFRA-25629](https://issues.apache.org/jira/browse/INFRA-25629), [INFRA-23946](https://issues.apache.org/jira/browse/INFRA-23946), [INFRA-23220](https://issues.apache.org/jira/browse/INFRA-23220), and [INFRA-23044](https://issues.apache.org/jira/browse/INFRA-23044) for some examples. @sarvekshayr will test the PAT approach on her fork, where she has permissions to create them. Once we have a POC running on the forks we can raise an infra ticket to get a PAT for ozone-site and store it as a secret in the Ozone repo. This workflow can then reference the secret. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
