Thread by @mianbsp

How can a reviewer get a quick overview of a pull request?
One possibility is to provide the pull request directly in a test environment.
For our open source project #bestofui5 on GitHub we provide the pull requests ad hoc directly as an #Azure Static Web App.
How? 👇

In general, we use the possibilities of GitHub Actions, Azure Static Web Apps and Azure CLI here. Especially because these can be used free of charge.
The app is an #OpenUI5 app.
github.com/ui5-community/…
The data comes from another GitHub repository.
github.com/ui5-community/…

It does not make sense to provide this for all PRs.
So that the user can easily trigger the deployment, we have created a label for this.
When the label is added to a PR, an Azure Static Web App is created, a build is performed and this build is deployed.
github.com/ui5-community/…

It´s also possible to let the GitHub Action 'Azure/static-web-apps-deploy' build the app, in this case we do it before hand manually.
In this action, the app is identified by the api token.
After the successful build, the action will comment a public link to the app in the PR.

Now when the PR is updated, a new build is also automatically triggered.
github.com/ui5-community/…
If the PR is now closed or merged, the static app is then also automatically deleted.
github.com/ui5-community/…

Thus, it is much easier for contributors and reviewers to check the changes.
You can see a test PR here:
github.com/ui5-community/…
The documentation for that is here:
github.com/ui5-community/…

I see @lechnerc77 is always interested in that kind of stuff :)

The big advantage of this setup:
Since we generate a new static app each time and have no further dependencies towards Azure, we can deploy more Pre-production environments than provided in the free plan.
Only three environments are provided per app
docs.microsoft.com/en-us/azure/st…