[#2285] Add post-deployment test actions

[CYX22222003]

Fix reposense/RepoSense#2285

Proposed commit message

Add post-deployment test

Currently, deployments need to be tested manually, which can open
room
for errors in deployment in production

Let's use Lighthouse CI to audit the deployed web page. 

Other information

Information about lighthouse CI action:
https://github.com/treosh/lighthouse-ci-action

Sample test log:
https://github.com/CYX22222003/RepoSense-user-experiment-cyx/actions/runs/13253442029/job/36995960904
https://github.com/CYX22222003/RepoSense-user-experiment-cyx/actions/runs/13256746216/job/37004806285

[sopa301]

Thanks for looking into a solution for this! However, this seems to run on the publish-RepoSense CI. We should add it to the main RepoSense CI instead (because we want it to run on RepoSense PRs to ensure that publish-RepoSense works before merging on RepoSense).

[CYX22222003]

Thanks for looking into a solution for this! However, this seems to run on the publish-RepoSense CI. We should add it to the main RepoSense CI instead (because we want it to run on RepoSense PRs to ensure that publish-RepoSense works before merging on RepoSense).

Just want to clarify, so what the issue is referring to is actually a post deployment test on the previewed website of each PR to the main RepoSense repository?

In addition, I also notice that our previewed webpage is built using surge which seems to be not so reliable. Will this potentially affect the post-deployment test?

[sopa301]

Basically, we're trying to test if a publish-RepoSense deployment of the branch of the main RepoSense works. It's a pre-merge check on each RepoSense PR that deploys via Github Actions (like how publish-RepoSense does), then checks that deployment to make sure it works.

Surge should not affect the test because we are testing the Github Actions deployment of the RepoSense PR.

[CYX22222003]

Basically, we're trying to test if a publish-RepoSense deployment of the branch of the main RepoSense works. It's a pre-merge check on each RepoSense PR that deploys via Github Actions (like how publish-RepoSense does), then checks that deployment to make sure it works.

Surge should not affect the test because we are testing the Github Actions deployment of the RepoSense PR.

OK, i will look at the relevant deployment script in the main repo and make modification there.

i would like to keep this PR alive for now.