samueleresca commented on issue #84: URL: https://github.com/apache/incubator-pekko-sbt-paradox/issues/84#issuecomment-1867645240
> > https://github.com/apache/incubator-pekko-site/wiki/Manual-Publishing#incubator-pekko-site > > I'm happy enough for an ASF contributor to temporarily take over the asf-staging branch and making commits directly to it - via PRs if they prefer. Anything merged to the `content` folder of that git repo will be pushed to https://pekko.staged.apache.org. The point of that `staged` website is to allow some experimental changes. > > We can reset the history on asf-staging branch when we have finished the experimentation. > > There is a way to properly fix this, its with a sbt-plugin akin to https://github.com/sbt/sbt-ghpages . The sbt-ghpages plugin already handles the logic of "publishing the generate site to a separate branch", it just needs to be modified to handle asf site specifics. @mdedetrich Could you please confirm if I'm thinking in the right direction: 1. Enable `sbt-ghpages` on `main` branch with the following configs: ```scala git.remoteRepo := "[email protected]:apache/incubator-pekko-site.git" ghpagesBranch := "asf-staging" // targeting staging branch ``` 2. Run (potentially throght the github actions) `sbt ghpagesPushSite` to publish the content in https://pekko.staged.apache.org/ 3. Once verifyied the `asf-staging` branch proceed by merging changes in `asf-site`. Still manual, which it makes sense -- 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]
