I assumed that Apache infrastructure required asf-site as the branch name. That is, the Jenkins job would only be able to push to that branch and the beam.apache.org contents will only be pulled from that branch name.
On Tue, Oct 2, 2018, 09:04 Scott Wegner <[email protected]> wrote: > The plan is to have javadocs/pydocs on a branch inside this repo. The > implementation I have in progress creates a new release-docs branch with > these docs moved up to the top of the directory structure. That work is > staged here: https://github.com/swegner/beam-site/tree/release-docs > > The exact branch we use, whether asf-site or release-docs doesn't really > matter. We are currently publishing the website from asf-site, so the > migration is trickier if we want to reuse this existing branch. We could > flip back to asf-site after migration, although I sort of like having a > different branch name to avoid confusion with the apache/beam asf-site > branch. > > Thoughts? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/apache/beam-site/pull/567#issuecomment-426331601>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AAHyz5hhuKaxJ6sBYf4i30YFYZ3Jrw_lks5ug46VgaJpZM4XCoiQ> > . > [ Full content available at: https://github.com/apache/beam-site/pull/567 ] This message was relayed via gitbox.apache.org for [email protected]
