[FEAT] Added doc portal pr preview - #296
Merged
Merged
Conversation
Contributor
|
thomasbaronnet
commented
Sep 10, 2026
thomasbaronnet
commented
Sep 10, 2026
thomasbaronnet
requested review from
Fenkiou,
MatthieuMoreau0,
MohamedAminMallek and
Zakubo
September 10, 2026 12:41
MohamedAminMallek
approved these changes
Sep 11, 2026
Fenkiou
reviewed
Sep 11, 2026
Fenkiou
reviewed
Sep 15, 2026
Fenkiou
approved these changes
Sep 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Add a doc portal preview on PRs (next to the mkdocs one).
We pull the doc-portal image, build it with the PR mkdocs URL + ASTRO_BASE, and publish it under portal-preview/pr-/. When the PR is closed we clean it up.
Remaining Tasks
Related PRs in other projects (PASQAL developers only)
Additional merge criteria
Breaking changes
Checklist
Versioning (PASQAL developers only)
VERSION.txtfollowing the changes in your PR and by using semantic versioning.Documentation
Tests
Internal tests pipeline (PASQAL developers only)
If your PR hasn't changed any functionality, it still needs to be validated against internal tests.
After updating the version (PASQAL developers only)