You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@arrow.apache.org by GitBox <gi...@apache.org> on 2019/09/09 23:26:39 UTC

[GitHub] [arrow-site] nealrichardson opened a new pull request #21: ARROW-6497: [Website] On change to master branch, automatically make PR to asf-site

nealrichardson opened a new pull request #21: ARROW-6497: [Website] On change to master branch, automatically make PR to asf-site
URL: https://github.com/apache/arrow-site/pull/21
 
 
   See background on the [ticket](https://issues.apache.org/jira/browse/ARROW-6497). Summary: INFRA won't let us add a deploy key for Travis to automatically publish to asf-site, so this works around it by publishing to a fork and making a PR from that fork back to apache/arrow-site. 
   
   I created a new bot GitHub user, `arrow-site-bot`, and gave it access only to the ursa-labs/arrow-site repository. That way, the personal access token it has is effectively limited in scope to that single repository (fork). All that is required is enabling Travis-CI for apache/arrow-site--no additional secrets or credentials.
   
   To test this out, [I used my fork as "upstream"](https://github.com/nealrichardson/arrow-site/commit/772983a0b38bfa17197eac1a0238a9b81704f4a5) and made https://github.com/nealrichardson/arrow-site/pull/2.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services