pdpotter commented on issue #94: URL: https://github.com/apache/age-website/issues/94#issuecomment-1280431297
I don't quite understand how a commit on the master branch, triggering the `Build documentation` action, affects changes on the website to be rolled back. The last two deploys after a commit on the master branch (https://github.com/apache/age-website/commit/39f4ad4f29864181987cea90048d423969a42ec6 and https://github.com/apache/age-website/commit/562fe1d9ecdf1957d42419a9a95a469c010a9943) only make changes to the `age-manual` directory in the `asf-site` branch. This `asf-site` branch contains the html files (and css an js) that are used for the website. I did detect a rollbacks when changes in the `new-site` branch are made, as in the triggered `build gatsby` action, all files and directories in the `asf-site` branch are overridden. The `build gatsby` action does not build other versions of the documentation than `master` (e.g., `v0.6.0`). https://github.com/apache/age-website/pull/90 should solve this issue. In the future, the `age-dev-manual` folder that would be created by the `Build documentation` action in the `developer-manual` branch would be overridden as well, so an additional build step should be added to the workflow to rebuild this documentation as well. @JoshInnis did you remove the action in the `developer-manual` branch (https://github.com/apache/age-website/commit/390e6d39c8672de7a67f41c4d6415c9c69bf5667) because it rolled back changes in the website? It would be easier and faster if the `build gatsby` action triggered by the `new-site` branch wouldn't overwrite the `age-manual` and `age-dev-manual` folders, but I haven't found a way to do this. -- 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]
