[
https://issues.apache.org/jira/browse/LUCENE-9013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16961066#comment-16961066
]
Adam Walz commented on LUCENE-9013:
-----------------------------------
Force pushing would definitely be the easier route instead of doing a dance
with default branches.
For github pages I read on LUCENE-8987
{quote}we can take PRs from the public (with GitHub preview of pages)
{quote}
And didn't quite understand the goal. Without gh-pages the preview would be of
github flavored markdown, but not a preview of the compiled site. However, even
with gh-pages there wouldn't really be a preview since you would have to either
wait for jenkins to build and deploy to that branch, or take two PRs (one for
each branch).
Since you already have ASF jenkins building a staging site I don't see anything
that is really gained by also having gh-pages, so let's not merge that fork.
Just a misunderstanding of the wording from the parent Jira ticket.
> Migrate existing site content (except javadoc, refguide)
> --------------------------------------------------------
>
> Key: LUCENE-9013
> URL: https://issues.apache.org/jira/browse/LUCENE-9013
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Jan Høydahl
> Priority: Major
>
> Resulting in a successful local build
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
